debug: add debug_getBlockReceipts with EIP-8037 dimensional gas fields

[qu0b]

Summary

Mirrors eth_getBlockReceipts. When EIP-8037 is active, each receipt also carries stateGasCharged (pre-refund state-dimension gas) and stateGasRefunded (state-dimension refunds applied). Pre-activation blocks omit both fields.

Header reconstruction (MUST):

header.stateGasUsed   = Σ stateGasCharged − Σ stateGasRefunded
header.regularGasUsed = Σ gasUsed         − header.stateGasUsed

Motivation

bal-devnet-6 clients diverged on regular-vs-state gas attribution by exactly AccountCreationCost = 131,488 because the missing tx-level CREATE-halt refund (now fixed in ethereum/EIPs#11611) was invisible at the receipt level. The current Receipt exposes only the unified gasUsed — a missed refund and "no state operations" produce the same number.

The split stateGasCharged / stateGasRefunded makes the failure mode directly observable at receipt scope. A consumer can verify header.stateGasUsed reconstructs from the receipts and localise any divergence to a specific tx without running a tracer.

Tracking issue: ethereum/execution-specs#2804.

Design choices

• Two fields, not six. regularGasUsed is derivable as gasUsed − (stateGasCharged − stateGasRefunded); cumulative* fields are derivable by summing per-tx values in order. Only the two non-derivable, state-dimension counters are spec'd.
• Split stateGasCharged + stateGasRefunded, not a signed net. Per EIPs#11611, execution_state_gas_used may go negative under EIP-7702 unset. JSON-RPC convention is unsigned hex. A single net stateGasUsed would have to be either signed (parser-hostile) or clamped (data loss — "no state ops" indistinguishable from "charge + larger refund"). The split is the only encoding that's both parseable and lossless.
• No regular-dim refunds. EIP-8037 (per EIPs#11573) removes all regular-dimension refund pathways; regular gas is pay-as-you-go. No field is needed for the regular dim — it's already covered by gasUsed.
• Pre-activation: fields omitted (not zero). Eliminates absent-vs-zero ambiguity for downstream consumers.
• debug namespace, additive. No receipts-root change, no consensus impact. Once cross-client implementations are stable, the same two fields can land on eth_getBlockReceipts / eth_getTransactionReceipt without rename.

Implementation cost

Both clients already compute the dimensional values during execution:

• geth core/vm/gascosts.go has GasBudget{RegularGas, StateGas, StateGasRefund} and threads it through state_transition.go. The StateGasRefund accumulator already exists per-frame. Receipt struct (core/types/receipt.go) is single-dim today; the wiring is the new work.
• reth crates/ethereum/payload/src/lib.rs tracks block_state_gas_used (net) at payload-build time. Persisted receipt is alloy_consensus::EthereumReceipt, single-dim. Splitting state_gas_used() into charged + refunded requires a revm change.

Per-client wiring is small. No new tracing infrastructure required (geth's core/tracing/hooks.go:171 has an unlanded GasChangeV2Hook TODO — this PR doesn't depend on it).

[qu0b]

Closed for now, clients are not in favor of this new endpoint, but would rather implement a Tracer that displays the state gas.