Fix CI/CD workflow to use correct Python versions and PyPI URL

[nick-gorman]

• Pass matrix python-version to setup-uv, uv sync, and uv run so tests actually run against the specified Python versions
• Remove Python 3.9 from matrix (requires-python is >=3.10)
• Fix PyPI publish URL from isp-workbook-parser to ispypsa
• Bump actions/checkout to v4 and astral-sh/setup-uv to v5

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[dylanjmcconnell]

FYI I dropped tables as a dependency (apparently not used?) .. upgraded pyproj (..there were actually 3.14 wheels for next minor version of pyproj - 3.7.2) and re-upgraded upgrade to 3.14 and it all seemed to work.

But basically ended up with a somewhat semi issue with shapely (particularly on macos it seems). As with pyproj and upgrade is possible, but doesn't work with the pinned version of PyPSA (0.34.1 need shapely <2.1). Think only solution here is to wait until we (eventually) upgrade to PyPSA >1.0 - looks like that would work. So downgraded again.

Seems to be working on linux/macos - no idea why it's not with windows am afraid.

p.s. an another / unrelated issue (maybe best dealt with somewhere else?) - seems like the test are touching / changing one of the data files in the testing data directory (specifically tests/test_model/test_pypsa_friendly_inputs/test_custom_constraints/demand_traces/bus_two.parquet - seems to be modified after running tests, but haven't checked what's going on there).

Any way tl;dr is tried to fix, but failed (at least on windows)

[nick-gorman]

Thanks @dylanjmcconnell, I tracked the windows failure down to a numpy versioning (build) issue.

Looks good now. Note, I removed 3.10, which is technically a breaking change, but I guess we are allowed to do that because ISPyPSA isn't stable.

Let me know if you have any other comments before we push.

[dylanjmcconnell]

Hey Nick - given upgrade to pypsa to 1.0, the issue identified above would be addressed (namely that an updated version of shapely can be installed, i.e. one that has 3.14 wheels, and will works with the updated pypsa.)

I think given this (and that this PR is upstream of the 'pyspa-upgrade' PR) - think it makes most sense to merge this PR (then rebase upgrade-pypsa onto the updated main), then add 3.14 to the upgrade-pypsa PR*

(*Haven't had a chance to properly look at that - seems okay, but maybe need to have a better look / review too)

[nick-gorman]

@dylanjmcconnell, your suggested sequencing makes sense to me, I'll merge this PR.