Transition build system from `hatch` to `uv`

[adamamer20]

We currently rely on hatch for building and packaging, but uv is both faster and easier to use, simplifying dependency resolution and upgrade. Since we’re already using uv in our build and test workflow (build.yml), we should change our pyproject.toml and publish.yml to use uv instead of hatch.

[Corvince]

I think this will be a good direction and also something to do for mesa itself. But I would probably wait until uv also includes a build backend, so we can fully switch to uv. Right now uv build is just a build frontend that uses hatchling by default. But they are working on a uv build backend, so maybe wait a bit more and then migrate that also. astral-sh/uv#8779