Add EIP-7928 Block-level Access Lists JSON RPC methods

[nerolation]

Add RPC methods for EIP-7928 Block-level Access Lists

This PR introduces two new RPC methods to query block-level access lists (BALs) as defined in EIP-7928:

• eth_getBlockAccessListByHash — returns the BAL for a block by hash
• eth_getBlockAccessListByNumber — returns the BAL for a block by number or tag

---

• Block access lists are stored separately from EL blocks and are not included in the Block structure.
• RPC methods use the BlockAccessList naming to avoid confusion with EIP-2930 transaction access lists.
• Error code 4445 is returned for pre-Amsterdam blocks.

[MysticRyuujin]

Is there a test for 4444 "pruned history unavailable" or perhaps that not possible with the current hivenet?

Also, maybe a silly question but how will the node know the difference between non-existing and pruned?

Otherwise lgtm

[nerolation]

No, there's none on that. Wasn't sure about this one but if you say it makes sense to add one, let's do it.
Re, pruned vs. non-available, there can never be a valid ExecutionPayloadEnvelope with an empty Payload on the CL . As long as the EL block exists, it will always contain some fields in the BAL, e.g. entries from system contracts (4788, 7002, ... ) and won't be empty. If the BAL doesn't exist, but the block did, it must have been pruned.

[mkalinin]

The spec and tests look good!