Switch to hatch-vcs for versioning

[vidipsingh]

Description

This PR implements hatch-vcs for versioning, enabling automatic versioning based on Git tags.

Related to: #4742

Type of change

• New feature (non-breaking change which adds functionality)
• Optimization (back-end change that speeds up the code)
• Bug fix (non-breaking change which fixes an issue)

Key checklist:

• No style issues: $ pre-commit run (or $ nox -s pre-commit) (see CONTRIBUTING.md for how to set this up to run automatically when committing locally, in just two lines of code)
• All tests pass: $ python -m pytest (or $ nox -s tests)
• The documentation builds: $ python -m pytest --doctest-plus src (or $ nox -s doctests)

You can run integration tests, unit tests, and doctests together at once, using $ nox -s quick.

Further checks:

• Code is commented, particularly in hard-to-understand areas
• Tests added that prove fix is effective or that feature works

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.69%. Comparing base (5e6678b) to head (3ba901f).
Report is 1 commits behind head on develop.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #4802   +/-   ##
========================================
  Coverage    98.69%   98.69%           
========================================
  Files          303      303           
  Lines        23258    23258           
========================================
  Hits         22955    22955           
  Misses         303      303           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[kratman]

Look at the "update_version.py" script in PyBaMM. A bunch of files are updated. For this to work you also need to get the other updated files working for releases.

Files like the change log will still need to be update for each release

[vidipsingh]

Look at the "update_version.py" script in PyBaMM. A bunch of files are updated. For this to work you also need to get the other updated files working for releases.

Files like the change log will still need to be update for each release

Thanks for the heads-up, @kratman! I'll look into the update_version.py script and other relevant files to ensure everything works properly for releases.

[Saransh-cpp]

Can we move this down to the already existing tool.hatch section?

Suggested change

	[tool.hatch.version]
	source = "vcs"
	[tool.hatch]
	version.source = "vcs"
	build.hooks.vcs.version-file = "src/pybamm/_version.py"

[vidipsingh]

Sure, I'll move it to the tool.hatch section.