feat(tests): add EIP-8357 registry coverage

[lucadonnoh]

Description

Adds draft execution-spec test coverage for EIP-8357, the EVM verification-key registry.

• Defines the registry constants, runtime bytecode, initcode, deployment salt, and reference EIP version.
• Verifies deterministic deployment through the EIP-7997 factory at the specified registry address.
• Covers current, exact-current, and historical reads.
• Covers initial registration, subsequent registration, and historical-key reactivation.
• Covers invalid keys, timestamps, calldata lengths, duplicate registration, unregistered reactivation, and nonzero value.
• Checks complete return data and exact registry state changes through a result-recording contract.

This draft is intentionally stacked on projects/zkevm because EIP-8357 identifies fork-selected EVM verification keys for the zkEVM/stateless-validation work tracked in #2268. Please advise whether an eips/amsterdam/eip-8357 integration branch should be created later.

Fork-boundary activation, checked system-call execution, and system-call gas accounting are deliberately not included yet.

Related Issues or PRs

• Add EIP: EVM Verification Key Registry EIPs#12055
• Tracking PR for projects/zkEVM #2268

Validation

• uv run fill --fork Amsterdam tests/amsterdam/eip8357_verification_key_registry --output <temporary-directory>: 78 passed.
• All commands in the just static recipe passed when run directly: mypy, EELS import isolation, codespell, vulture, actionlint, lock check, Ruff formatting, and Ruff lint. (just itself is not installed locally.)
• The referenced EIP blob hash matches the current EIP-8357 document.

Checklist

• Ran the repository's fast static checks.
• PR title has the form <type>(<area>): <title> and matches the intended squash commit.

Cute Animal Picture

Bonnet macaque photographed by Augustus Binu in 2015 (Wikimedia Commons).