Switch to hatchling as the build backend, and use hatch-vcs for versioning

[agriyakhetarpal]

Post #4487, PyBaMM is now a pure Python package – this means we should move away from the setuptools build backend and switch to hatchling – which is arguably the better choice. With #4216 complete, it is also possible to single-source the package version, and use versioning based on Git tags. This is possible with hatch-vcs, which relies on setuptools-scm internally).

See also:

• https://www.pyopensci.org/python-package-guide/package-structure-code/python-package-build-tools.html#hatch
• https://www.pyopensci.org/python-package-guide/package-structure-code/python-package-versions.html#tool-2-hatch-vcs-hatchling-build-back-end
• https://github.com/ofek/hatch-vcs
• https://hatch.pypa.io/1.13/plugins/version-source/reference/