ci: install setuptools directly instead of via extra-build-dependencies

uv pip install did not pick up [tool.uv.extra-build-dependencies] (same
"No module named 'setuptools'" error, with the same hint, reappeared
on the next run) - that config apparently only applies to uv's
project-aware resolver (uv sync/lock), not the pip-compatible
uv pip install used here. Installing setuptools into the venv directly
before the --no-build-isolation gdal build is the other fix uv's error
suggested, and doesn't depend on that.

Author: lachlangrose

.github/workflows/packages.yml

@@ -106,6 +106,7 @@ jobs:
         run: |
           uv sync --package map2loop --extra tests --python ${{ matrix.python-version }}
           GDAL_VERSION=$(gdal-config --version)
+          uv pip install setuptools
           uv pip install "gdal==${GDAL_VERSION}" --no-build-isolation-package gdal
 
       - name: pytest

pyproject.toml

@@ -94,13 +94,6 @@ loopstructuralvisualisation = { workspace = true }
 map2loop = { workspace = true }
 LoopStructural = { workspace = true }
 
-[tool.uv.extra-build-dependencies]
-# gdal is installed with --no-build-isolation-package (see packages.yml) so
-# its setup.py can see the venv's numpy and build the _gdal_array extension;
-# that also means it no longer gets setuptools for free from an isolated
-# build env, so it must be declared here.
-gdal = ["setuptools"]
-
 [tool.pytest.ini_options]
 addopts = "--import-mode=importlib"
 testpaths = ["tests"]