chore: Replace hardcoded version with automatic git tag versioning

[jcpitre]

Switches from manually maintaining version numbers in source files to automatic versioning driven by git tags using hatch-vcs.

Changes

• Add hatch-vcs as a build dependency in pyproject.toml
• Remove hardcoded version field; use dynamic = ["version"] instead
• __init__.py now reads version from package metadata at runtime
• CI release workflow uses fetch-depth: 0 so hatch-vcs can resolve tags during build
• Update version test to check program name instead of a hardcoded version string

How to release going forward

Create a GitHub Release with a tag like v0.2.0 — the workflow picks it up and publishes that version to PyPI automatically. No more manual version bumps.

Testing

This will be tested once merged and a release is done.

[cka-y]

[question] does this require updating the readme documentation on how to release a new version?

[davidgamez]

🥇

[jcpitre]

[question] does this require updating the readme documentation on how to release a new version?

Modified the README.md