AIFINP-223/224: sync deployments and implement version switchers

[coinsecuritiescompany]

Summary

• implements AIFINP-223 environment and protocol-version switcher
• EVM auto prefers enabled v1.4 and falls back to a known production v1.2 deployment
• explicit v1.4 and v1.2 never substitute another version
• restricts EVM development resolution to Amoy
• imports EVM v1.4 metadata from AIFINP-223: quarantine unsafe v1.4 deployments evm-contract#33
• updates Solana devnet/mainnet program IDs from e5df8f5436cf646ab495381eee04e0d1a10b4e2f
• adds one static EVM/Solana registry, schema and deterministic generator
• adds Robinhood v1.4 metadata and excludes BOT Chain from v1.4
• corrects Polygon 0x2791… identity to USDC.e and quarantines invalid Base v1.4
• exposes typed unavailable/disabled deployment errors

Verification

• GitHub Actions: rerunning against the corrected AIFINP-223 matrix
• TypeScript build: PASS
• registry drift and source-provenance checks: PASS
• resolver/provenance tests: 43/43 PASS
• explicit v1.4 quarantine behavior: covered
• automatic v1.2 fallback: covered
• package version gate: 2.0.0-rc.15

Release restriction

Production v1.4 EVM and Solana deployments remain disabled pending their activation gates. EVM auto keeps the Jira-required legacy v1.2 fallback; callers that require v1.4 must request version: "v1.4". No mainnet transaction is included.

[coinsecuritiescompany]

Re-read the full AIFINP-223 acceptance criteria and corrected the resolver. EVM auto now prefers enabled v1.4 and falls back to a known production v1.2 deployment when v1.4 is absent, disabled, or invalid. Explicit v1.4 remains exact and throws instead of downgrading; development remains Amoy-only. Local build, registry checks, and the 43 resolver/provenance tests pass.