feat: rollup mana limit gas validation

[mrzeszutko]

Summary

Transactions whose gas limits exceed the block or checkpoint mana limit are currently silently dropped during block building, causing users' .wait() calls to hang indefinitely. This PR adds early rejection at the gossip, RPC, and pending pool entry points by validating both L2 and DA gas limits against protocol limits and operator-configured validator block gas limits.

Changes

Promote rollupManaLimit to L1RollupConstants

• Added rollupManaLimit: number to the L1RollupConstants type, EmptyL1RollupConstants (defaults to Number.MAX_SAFE_INTEGER), and the Zod schema
• Removed the ad-hoc & { rollupManaLimit?: number } extensions from the archiver, sequencer, and block-builder types — they now get it from the base type
• Updated EpochCache.create() and RollupContract.getRollupConstants() to fetch and include rollupManaLimit from L1

Validate L2 and DA gas limits at tx entry points

• GasLimitsValidator now accepts { rollupManaLimit?, maxBlockL2Gas?, maxBlockDAGas?, bindings? }:
  • Effective L2 limit = min(MAX_PROCESSABLE_L2_GAS, rollupManaLimit, maxBlockL2Gas)
  • Effective DA limit = min(MAX_PROCESSABLE_DA_GAS_PER_CHECKPOINT, maxBlockDAGas)
  • rollupManaLimit applies to L2 gas only (not DA)
• GasTxValidator forwards these options to its inner GasLimitsValidator
• All factory functions (createFirstStageTxValidationsForGossipedTransactions, createTxValidatorForAcceptingTxsOverRPC, createTxValidatorForTransactionsEnteringPendingTxPool) accept and pass through the limits

Use validator block gas limits for tx validation

The existing VALIDATOR_MAX_L2_BLOCK_GAS and VALIDATOR_MAX_DA_BLOCK_GAS env vars (introduced in #21060 for block proposal validation) are now also used for tx acceptance validation. Derived block limits (from the sequencer timetable) are only used for proposals — not for validation.

• P2P config: Added validateMaxL2BlockGas and validateMaxDABlockGas fields reading the existing VALIDATOR_MAX_L2_BLOCK_GAS / VALIDATOR_MAX_DA_BLOCK_GAS env vars
• Gossip path (libp2p_service.ts): Passes rollupManaLimit from L1 constants and validator block gas limits from P2P config
• RPC path (aztec-node/server.ts): Passes rollupManaLimit from L1 constants and validator block gas limits from node config
• Pending pool migration (client/factory.ts): Passes rollupManaLimit and validator block gas limits from config

Unit tests

Tests in gas_validator.test.ts covering:

• Rejection when exceeding rollupManaLimit (L2), maxBlockL2Gas, or maxBlockDAGas
• Min-of-all-limits behavior (L2)
• Acceptance at exactly the effective L2 and DA limits
• Fallback to MAX_PROCESSABLE_L2_GAS / MAX_PROCESSABLE_DA_GAS_PER_CHECKPOINT when no additional limits are set
• Forwarding L2 and DA limits through GasTxValidator

Notes

• When VALIDATOR_MAX_L2_BLOCK_GAS / VALIDATOR_MAX_DA_BLOCK_GAS are not set, only the protocol-level limits (MAX_PROCESSABLE_L2_GAS, MAX_PROCESSABLE_DA_GAS_PER_CHECKPOINT) and rollupManaLimit (L2 only) are enforced
• No new env vars — reuses the existing VALIDATOR_MAX_L2_BLOCK_GAS and VALIDATOR_MAX_DA_BLOCK_GAS from feat(validator): add VALIDATOR_ env vars for independent block limits #21060
• ~20 test files updated to include rollupManaLimit in their L1RollupConstants objects

Fixes A-68
Fixes A-639

[spalladino]

We shouldn't go the deriveMaxBlockL2Gas route. Instead. we should use the validator block gas limits introduced in #21060 (if set). The derived limit should only be used for proposals.

Also, it'd be good to extend this check to DA limits as well since we're at it.

[AztecBot]

✅ Successfully backported to backport-to-v4-staging #21187.