Switch to hatch as a build backend, environment manager and publishing tool

We should consider switching to [hatch](https://hatch.pypa.io/1.12/) to simplify our setup and reduce the number of tools we use:

- setuptools
- twine
- tox

See [here](https://hatch.pypa.io/1.12/why/) for a comparison to other tools and reasons for using hatch.

The issue proposes replacing setuptools, twine, and tox with hatch. Start by reading the project's current pyproject.toml and setup.cfg files to understand the build configuration. Review hatch's documentation on migration from setuptools and tox. Test the migration in a local environment to ensure the build, testing, and publishing workflows still work. 'Done' looks like a working hatch configuration that replicates all existing functionality.

Rédigé par le modèle d'indexation à partir du texte de l'issue.