beacon api v2.5.0 compatibility

[errge]

Rationale

There is a change in the beacon api between 2.4.2 and 2.5.0: https://github.com/ethereum/beacon-APIs/blob/v2.5.0/apis/beacon/rewards/attestations.yaml#L34

The field called "execution_optimistic" is now required, and erigon doesn't provide it.

Therefore, if the API is used from a strict swagger generated client, we get an exception here, because erigon's answer is strictly speaking incorrect.

As a backstop, one can regenerate the client with 2.4.2 for now.

I also have a general question about this: I didn't find any documentation inside the repo or anywhere, that what is supposed to be the officially implemented beacon api version. This might be very useful for people, who want to call the API programatically through swagger, not just with small random curl or hand-programmed requests.

Implementation

I have no idea about the implementation and beacon api version inside erigon.