fix: detect modern vyper version pragmas

[banteg]

Motivation

Current Vyper accepts source compiler constraints in both legacy # @version ... comments and modern # pragma version ... comments. ape-vyper only recognized the legacy spelling, so modern Vyper sources could be grouped with no-pragma sources and compiled with the wrong selected compiler before Vyper itself validated the source constraint.

Vyper also changed the version-pragma grammar across releases: v0.3.9 and earlier use npm-style semantic version specs, while v0.3.10 and newer use packaging.specifiers.SpecifierSet-style rules after caret translation. Ape needs to use the rules for each candidate compiler version, otherwise compiler selection can accept or reject a pragma differently than Vyper would.

Malformed present pragmas now fail early as VyperCompileError instead of being treated as missing pragmas.

Code References

• Vyper validates version pragmas in validate_version_pragma().
• Vyper parses modern # pragma version.
• Vyper still accepts legacy # @version.
• Vyper keeps compiler_version source-only, not a compiler input.
• Vyper tests cover valid/invalid specs, file-specific errors, #pragma version, and import validation.
• Historical Vyper v0.3.9 used NpmSpec; v0.3.10 switched to SpecifierSet.

Summary

• Recognize both # @version ... and # pragma version ....
• Preserve whitespace tolerance for #pragma version ....
• Match candidate compiler versions using Vyper's release-specific grammar: npm-style for <0.3.10, PEP 440-style for >=0.3.10.
• Add semantic-version for the legacy npm-style grammar.
• Raise a clear VyperCompileError when a present version pragma cannot be parsed.
• Add focused parser and version-map coverage, including cases adapted from Vyper's pre-parser tests.

Tests

• git diff --check
• uv run --group lint ruff check .
• uv run --group lint ruff format --check .
• uv run --group lint --group test mypy .
• uv run --python 3.11 --group test python -m py_compile ape_vyper/_utils.py ape_vyper/compiler/api.py tests/functional/test_compiler.py
• uv run --python 3.11 --group test pytest tests/functional/test_compiler.py -q -k "version_pragma_spec or version_map_modern_pragma or version_map_invalid_pragma" (29 passed, 102 deselected)

Note: uv run --python 3.11 --group test pytest tests/functional/test_compiler.py -q was also attempted locally. The compile-heavy cases failed after vvm.get_installable_vyper_versions() hit the GitHub API rate limit, leaving no installable 0.4.x compiler for the existing 0.4 fixtures. The focused parser/version-map coverage above passes.

[antazoey]

This is wrong for post 1.0 vyper

[banteg]

this is a direct port of how vyper itself does it https://github.com/vyperlang/vyper/blob/c219e6be2f230931be19a8eb945dc432538f9245/vyper/ast/pre_parser.py#L30

from my understanding ^1.0.0 in semver is >=1.0.0 <2.0.0
while the rewritten ~=1.0.0 in pep440 becomes >=1.0.0 <1.1.0