Modernize project for compatibility with uv

[jbcoe]

Closes #70.

[jbcoe]

@StephenOman we have failing tests where the virtual environment does not have the packages (pytest etc) to run tests. We can fix these failures by installing the missing packages in the relevant virtual environment but I'm a little unclear as to what the failing tests are intended to test. We already have tests passing which run tests from a developer-like virtual environment (set up with dev dependencies using uv).

[StephenOman]

These tests are supposed to test the distributions (source distribution and ManyLinux wheel) that would be available from PyPI if released.

[heiner]

Nice! In a future change, it's probably possible to remove setup.py entirely by switching the build system to build-backend = "scikit_build_core.build", i.e. this. This would remove the custom build logic by adding a minor amount of indirection.

[jbcoe]

I've made significant progress with the sci-kit build setup already. I can set up a PR if you're able to offer input?

[heiner]

In the interest of small PRs I'd suggest landing this one first, then doing sci-kit build in the next one?

[jbcoe]

Totally agreed. This PR is big enough as is and I don't have the sci-kit build setup working perfectly yet.

[StephenOman]

Quick question, is this change a breaking change? Can people still install and build without uv?

Also, perhaps we should add uv instructions to the documentation.

[heiner]

Any tool that is compatible with https://peps.python.org/pep-0621/ should be able to build and install the package; that includes pip.