10146 gloas execution payload gossip rules

[mehdi-aouadi]

PR Description

Add Gloas execution_payload gossip rules

Fixed Issue(s)

#10146

Documentation

• I thought about documentation and added the doc-change-required label to this PR if updates are required.

Changelog

• I thought about adding a changelog entry, and added one if I deemed necessary.

---

Note

Implements Gloas execution payload gossip validation (including signature, slot, bid consistency, and deduping), wires it into the controller, and adds supporting APIs, constants, and tests.

• Gossip/Validation:
  • Implement ExecutionPayloadGossipValidator with pre-block checks, block-based bid consistency (builder_index, payload.block_hash), state-based signature verification, deduping via recent cache, and SAVE_FOR_FUTURE handling.
  • Use RECENT_SEEN_EXECUTION_PAYLOADS_CACHE_SIZE for seen-payload caches; remove local constant.
  • Wire validator in BeaconChainController and integrate with DefaultExecutionPayloadManager.
• Spec/API:
  • Add computeSigningRoot(ExecutionPayloadEnvelope, domain) in Spec.
  • Extend GossipValidationHelper with isBeforeFinalizedSlot, retrieveBlockByRoot, getStateAtSlotAndBlockRoot, and isSignatureValidWithRespectToBuilderIndex.
• Test Utilities:
  • Enhance DataStructureUtil to generate targeted ExecutionPayloadBid/SignedExecutionPayloadBid and related helpers.
• Constants:
  • Add RECENT_SEEN_EXECUTION_PAYLOADS_CACHE_SIZE in Constants.
• Tests:
  • Add ExecutionPayloadGossipValidatorTest covering accept, ignore, save-for-future, and reject paths.

^{Written by Cursor Bugbot for commit 5ee0d37. This will update automatically on new commits. Configure here.}

[zilm13]

LGTM, just few nits

[zilm13]

Rejecting here and in next logs

[zilm13]

It would be good to have test on this one to highlight the difference between isSlotFinalized and this one

[zilm13]

you already have shouldIgnoreIfAlreadySeen test, is this one needed?