Strip the free-threaded suffix before handing a version to uv

[SirHegel]

Fixes #2393.

Both places that build a uv command pass the environment's python setting straight to --python-version:

• src/hatch/env/lockers/uv.py (uv pip compile)
• src/hatch/env/virtual.py (uv pip sync)

uv resolves for a version, not for a build, so a free-threaded selector is not something it can parse:

$ uv pip compile pyproject.toml --python-version 3.14t
error: invalid value '3.14t' for '--python-version <PYTHON_VERSION>': Python version `3.14t`
could not be parsed: after parsing `3.14`, found `t`, which is not part of a valid version

hatch-test lists 3.14t in its default matrix (src/hatch/env/internal/test.py), so this is hit without any custom configuration.

The change

Run the value through normalize_distribution_name first. It is already used for exactly this in virtual.py::_get_available_distribution, and it only drops the suffix when the base version really has a free-threaded variant:

setting	passed to uv
3.14t	3.14
3.13t	3.13
3.14	3.14
3.9t	3.9t — 3.9 has no free-threaded build, left alone
pypy3.10	pypy3.10

Checked against uv 0.12.5: --python-version 3.14 compiles, 3.14t is the error above.

Tests

I did not add one. There is no existing harness for these two command builders — nothing in tests/ constructs a VirtualEnvironment or calls UVLocker._compile — and normalize_distribution_name is the tested part. Happy to add coverage if you would like it, but I did not want to stand up a fixture for it uninvited.

tests/env reports the same 187 collection errors before and after this change on my machine, so I could not use it as a signal either way; they look like a missing environment variable in my local setup rather than anything from this.