feat(l1): ef_tests: add standalone statetest, blocktest, and enginetest CLI runners

[spencer-tb]

Summary

Add three standalone CLI runners for direct execution of EEST fixtures, enabling consume direct integration without Hive. Each runner has --workers N, --run <regex>, --json, and --path <dir> flags.

Why new CLIs?

The existing test infrastructure uses either cargo test harnesses (datatest-stable for blockchain tests) or the state_v2 binary. Neither supports the flags needed for consume direct:

• datatest-stable harness — no --run regex filter, no --json output, no --workers control, hardcoded fixture paths. Can't be called as a standalone binary from EELS.
• state_v2 runner — creates a full Store (with background threads, trie cache, channels) per test case, making it 89x slower than necessary. State tests only need a HashMap → VM → check result.

The new runners are standalone binaries that EELS consume direct can invoke directly.

`ef_tests-statetest`

Fast state test runner using LEVM directly with in-memory HashMap state. No Store, no trie, no background threads — just loads pre-state into memory, executes one transaction, and verifies post-state accounts directly.

`ef_tests-blocktest`

Thin CLI wrapper around the existing `ef_tests-blockchain` crate. Calls `parse_and_execute()` per fixture file with rayon parallelism.

`ef_tests-enginetest`

Engine test runner for `blockchain_test_engine` fixtures. Routes payloads through the real Engine API RPC handler functions: `NewPayloadV1-V5Request.parse()` + `.handle(context)` and `ForkChoiceUpdatedV1-V4.handle(context)`. Same code path as `consume engine` via Hive, minus the HTTP transport layer.

Uses a shared `SyncManager`/`PeerHandler` via `OnceCell` to avoid thread exhaustion. Per-test `RpcApiContext` with isolated `block_worker_channel`.

Benchmarks

Tested against EEST v5.3.0 stable fixtures on Apple M-series.

`ef_tests-statetest` (36,220 tests):

Workers	Time	vs state_v2
8	3.8s	89x faster

`ef_tests-blocktest` (2,776 files, ~40k test cases):

Workers	Time	vs cargo test
8	28.7s	~same (now with CLI flags)

`ef_tests-enginetest` — exercises the same engine code paths as `consume engine` (40,521 tests):

Workers	Time
8	32.7s

100% pass rate across all three runners (3 known statetest failures from invalid CREATE blob transactions).

Usage

# State tests
ef_tests-statetest --workers 8 --path /path/to/state_tests/

# Block tests
ef_tests-blocktest --workers 8 --path /path/to/blockchain_tests/

# Engine tests
ef_tests-enginetest --workers 8 --path /path/to/blockchain_tests_engine/

# Filter by regex
ef_tests-enginetest --run "eip7702" --path /path/to/fixtures/

# JSON output for consume direct
ef_tests-statetest --json --workers 8 --path /path/to/state_tests/

Related: ethereum/go-ethereum#34650, erigontech/erigon#20315, NethermindEth/nethermind#11035, besu-eth/besu#10184, ethereum/execution-spec-tests#2319