[Build] Use setuptools_scm to allow git as the SSOT for package version

[shahar4499]

Instead of hardcoding the version into the repo, use git tags as the single source of truth for project's version, eliminating human error on releases.
To do this we can use setuptools_scm.

[AnnaRevutsky]

Hi! May I work on this issue?

[AnnaRevutsky]

Hi @shahar4499!

Can you please elaborate on the following points:

• What's the current release process you want to automate versioning for, if I understood correctly?
• Assuming you want the version to be determined by a git tag, which part of which flow (a github action presumably?) will produce the version artifact and where (github releases, pypi, the repo itself, etc)?

Thanks in advance,
Anna

[shahar4499]

Hey @AnnaRevutsky , sure! I'd be happy to guide you.

So basically right now, when releasing a version you have to do this in order:

1. bump the package's version in pyproject.toml
2. run uv sync
3. commit the pyproject.toml and uv.lock files
4. create a new tag + release via Github (only maintainers can do that)
5. the Github Action will run and publish it to PyPi

So, instead it would be better if pyproject.toml, and the package's init.py are not hardcoding any version, and are taking it from the git tag when a release is created.

setuptools_scm is supposed to allow this kind of CI workflow.

Does that make sense?