Add the "source" key as option to hatch.version

[relativityhd]

Hi all,
I noticed that the hatch.version.source option used by tools like uv-dynamic-versioning is not recognized by the json, even if it stated in the hatch documentation.
Hope this fix is the way you want it to be. :)

[github-actions]

Thanks for the PR!

This section of the codebase is owned by @madskristensen and @hyperupcall - if they write a comment saying "LGTM" then it will be merged.

[hyperupcall]

Thanks! The patch is great but it looks like CI is failing

[relativityhd]

@hyperupcall I needed to remove the overconstraint for the hatch-vcs case. Now the tests are working. I would interpret the docs of hatch so, that the "source" is an alternative to the "path" + "pattern" settings in all cases, not just hatch-vcs, thats why I think removing the overconstraint is correct.
However, I am not very deep into the topic, so I may be incorrect.

[ninoseki]

Just FYI for reviewers. Hatch's version source (= hatch.version.source) can have an arbitrary string (= a plugin's name).

For example, Hatch officially have regex, code and env plugins:

• https://hatch.pypa.io/1.13/plugins/version-source/regex/
• https://hatch.pypa.io/1.13/plugins/version-source/code/
• https://hatch.pypa.io/1.13/plugins/version-source/env/

And also there are 3rd party plugins like uv-dynamic-versioning. So allowing only vcs is not good.

[eggplants]

@hyperupcall Could you review this again? Tests are passed for now.

[hyperupcall]

Thanks! Sorry for the late merge