Be compatible with non-PEP440 version under env var UV_NON_PEP440_COMPAT

[JakkuSakura]

Summary

Under env var UV_NON_PEP440_COMPAT, the version parser will tolerate non-PEP440 versions like the legacy pip. This will probably fix #5478

Test Plan

Tests included

[codspeed-hq]

CodSpeed Performance Report

Merging #11434 will degrade performances by 13.14%

_{Comparing JakkuSakura:version-compat (5dac27b) with main (1cd9c37)}

Summary

❌ 1 regressions
✅ 13 untouched benchmarks

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

	Benchmark	BASE	HEAD	Change
❌	wheelname_tag_compatibility[flyte-short-incompatible]	771.4 ns	888.1 ns	-13.14%

[JakkuSakura]

Seems the CI for windows is random and unrelated

[charliermarsh]

I appreciate the PR but I'd prefer not to support this. It seems to be a violation of standards. What's the concrete problem you're trying to solve?

[JakkuSakura]

Understood. We are migrating our legacy python codebase to latest python version and ecosystem. Our versioning is non-standard because our codebase predates the standard. Having this feature help us to migrate our projects to uv. Without this, it's not possible to use tools other than legacy pip and setup.py. Fixing them one by one would take a long time.

I hoped to help other users with this PR, but fine just living in a fork