Add gloas worst-case block stress playbook

[barnabasbusa]

Adds playbooks/gloas-dev/worst-case-block.yaml, which reconstructs the worst-case SignedBeaconBlock from ethereum/consensus-specs#5436 (removal of MAX_DEPOSIT_REQUESTS_PER_PAYLOAD) by flooding every operation type at its per-block limit concurrently — deposit requests (default 16384, unbounded post-Gloas), 16 withdrawal requests, 2 consolidations, 64 builder deposits, 16 builder exits, 16 voluntary exits, 16 BLS changes, 16 proposer slashings, and 1 attester slashing — then asserts per-type that a block reached each limit (headline: a block carrying more than the old 8192 deposit-request cap) and that the chain still finalizes; on a giga-gas devnet the deposit knobs can be raised to 40000 to approach the ~10 MiB MAX_SIGNED_BEACON_BLOCK_SIZE bound. The playbook index diff includes catch-up regeneration for descriptions that had drifted on master.

⚠️ EIP-8282 builder deposit/exit contract addresses updated

This PR also updates the EIP-8282 builder contract addresses everywhere in assertoor (task defaults in generate_builder_deposits/generate_builder_exits, all gloas-dev playbooks, and the task READMEs) to the new sys-asm main CREATE2 addresses shipped in ethereum-genesis-generator v6.1.3 (ethpandaops/ethereum-genesis-generator#305):

Contract	Old (pre-devnet-7)	New (EGG ≥ v6.1.3)
Builder deposit	0x0000884d2AA32eAa155F59A2f24eFa73D9008282	0x0000bFF46984e3725691FA540a8C7589300D8282
Builder exit	0x000014574A74c805590AFF9499fc7A690f008282	0x000064D678505ad48F8cCb093BC65613800E8282

Heads-up for anyone running gloas playbooks: master still has the old addresses until this merges — on any devnet whose genesis was generated with EGG ≥ v6.1.3 (glamsterdam-devnet-7 onwards), builder deposits/exits from master's playbooks will target contracts that don't exist. Either use this branch or override builderDepositContract / builderExitContract in your playbook config.

[qu0b-reviewer]

🤖 qu0b-reviewer

All referenced parameters in the new playbook are confirmed to exist in the task configs. The PR is a well-formed playbook addition plus consistent contract-address updates across playbooks, READMEs, and Go defaults.

Summary of verification:

• Contract address updates (deposit 0x...D8282 and exit 0x...E8282) are consistently applied to Go config.go defaults, READMEs, and all playbooks — no stragglers of the old addresses remain anywhere.
• The new worst-case-block.yaml references tasks (run_tasks_concurrent, generate_batch_deposits, generate_exits, generate_bls_changes, generate_slashings, generate_withdrawal_requests, generate_consolidations, generate_builder_deposits, generate_builder_exits, check_consensus_block_proposals, generate_child_wallet, get_random_mnemonic) and all their config parameters — every one confirmed present.
• All check_consensus_block_proposals min-count assertion fields exist.
• Cross-task configVars references point to tasks with valid ids (spam_wallet, builder_mnemonic, get_specs); the two generate_slashings children inside run_tasks_concurrent are distinguished by config, not name — consistent with how the task stores children in a positional slice.
• The | jq-expression convention in configVars matches the existing established pattern in sibling playbooks (builder-lifecycle.yaml, builder-deposit-spam.yaml) and is valid jq after the auto-prepended ..

No grounded 🔴/🟡 findings.

---

_{Reviewed @ 124ae9b6
"If your only tool is a hammer, every problem looks like a microservice."}