feat(evm): port and replay-qualify Telos execution semantics on revm 41

[TheJudii]

Telos startup is deliberately blocked until the legacy execution rules are implemented on the revm 41 baseline and proven by replay. The detailed contract is in docs/telos/execution-compatibility.md on agent/production-bootstrap.

Implementation gates:

• Add Telos transaction primitives with chain-ID-3 sender recovery across live payloads, storage, stages, backfill, P2P/provider reads, and debug/trace replay; reject the forgeable format from public txpool admission.
• Implement the Telos revm transaction context, handler, opcode table, and frame hooks for fixed gas price, revision changes, first-new-address behavior, nonce exceptions, zero-address burn, beneficiary rules, BLOCKHASH, GASLIMIT, and PUSH0.
• Keep revmc/JIT disabled until it is independently shown to use identical Telos semantics.
• Persist parent-hash-keyed gas/revision schedules and a versioned, committed Engine sidecar needed for deterministic restart, reorg, backfill, and historical replay.
• Reject any local account or storage mutation absent from the authenticated native delta; reconciliation must prove completeness in both directions.

Verification gates:

• Add native golden vectors for every ambiguous historical rule and transaction boundary.
• Differentially test against the pinned Telos Reth 1.x/revm implementation.
• Replay all mainnet/testnet gas-price and revision transitions with receipt, log, block-hash, and sampled-state parity.
• Pass shallow/deep reorg, crash/restart, snapshot/resume, malformed-sidecar, and trace/RPC tests.
• Complete an independent consensus-correctness and security review.

The startup constant may be enabled only in the same reviewed change that supplies the passing evidence above.