Rewrite build.yml to better utilize uv

[dangotbanned]

What is your suggestion?

Been on my mind following (3513259) and (#3719)

I think we could simplify the workflow by using dependency-groups (Local dependencies for development).

So instead of all the branches where we conditionally install/uninstall stuff - we declare some groups to use in the workflow.

Example

We currently can only know what this environment actually resolves to by looking at the logs, after the run:

Maybe uninstall optional dependencies

altair/.github/workflows/build.yml

Lines 31 to 38 in 7c2d97f

	- name: Maybe uninstall optional dependencies
	# We uninstall pyarrow and vegafusion for one job to test that we have not
	# accidentally introduced a hard dependency on these libraries.
	# Uninstalling for Python 3.9 is an arbitrary choice.
	# Also see https://github.com/vega/altair/pull/3114
	if: ${{ matrix.python-version == '3.9' }}
	run: |
	uv pip uninstall pyarrow vegafusion vegafusion-python-embed vl-convert-python anywidget

Instead, we could define the state we're testing for by a new group:

[dependency-groups]
ci-no-optional = [
  # ...,
  # ...,
]

Then both build.yml and locally we can test this in the same way:

>>> uv sync --group "ci-no-optional"
>>> uv run tools/generate_schema_wrapper.py
>>> ...

Note

We would still have some branching, but that would only be passing in the --group/ --extra options.

Benefits

• Simpler workflow definition
• Ability to run the test locally
• Likely reduce workflow runtimes, since uv can reuse content from uv.lock (https://docs.astral.sh/uv/concepts/projects/sync/)

Have you considered any alternative solutions?

No response