Tracking: Update Beacon API to Electra

[saolyn]

Update Beacon API to Electra

These are the endpoints that we need to ensure are updated to Electra.

Missing Endpoints

• [x] /eth/v2/beacon/blocks/{block_id}/attestations
• [x] /eth/v2/beacon/pool/attester_slashings GET
• [ ] /eth/v2/beacon/pool/attester_slashings POST
• [x] /eth/v2/validator/aggregate_attestation
• [ ] /eth/v2/validator/aggregate_and_proofs
• [ ] /eth/v2/events

Endpoints to check

• [x] /eth/v1/beacon/blinded_blocks
• [x] /eth/v2/beacon/blinded_blocks
• [x] /eth/v1/beacon/blocks
• [x] /eth/v2/beacon/blocks
• [x] /eth/v2/beacon/blocks/{block_id}
• [x] /eth/v1/beacon/blob_sidecars/{block_id}
• [x] /eth/v1/beacon/blinded_blocks/{block_id}
• [x] /eth/v2/beacon/pool/attestations GET
• [x] /eth/v2/beacon/pool/attestations POST
• [x] /eth/v2/debug/beacon/states/{state_id}
• [x] /eth/v3/validator/blocks/{slot}

I checked all the above and they all appear to either be updated to Electra or do not contain any fork logic.

This issue should be closed after all of the above tasks are complete.

[james-prysm]

discussion from discord says we probably don't want to have a v2 of events, instead update the first version. still up for debate on the following

either have a new versioned event for the attestation and attester_slashing, or leave it up to the consumer to figure it out based on slot of the object(as suggested by... lion... i think) Are people wanting a versioned event for these 2, or do we let people figure it out from the slot?

[james-prysm]

We also need to update the validator client to use these endpoints otherwise running the vc in rest mode will fail