Added executionRequestsHash to EngineNewPayloadV4

[lucassaldanha]

PR Description

• Replaced ExecutionPayloadV4 for ExecutionPayloadV3 in EngineNewPayloadV4 (eventually ExecutionPayloadV4 will be deleted)
• Added new parameter executionRequestHash to EngineNewPayloadV4
• Updated ExecutionClientHandler.#engineNewPayload method with a new parameter slot. This is used to resolve the milestone later, replacing the old logic that was getting the milestone from the executionPayload
• Updated NewPayloadRequest object with a new optional field executionRequestsHash. Later this field will be populated by the hash of the requests in the beacn block body.

This PR is a preparation for the work where we need to calculate the hash of the execution requests in the beacon block body, and pass it on engine_newPayloadV4. In this PR, I am only updating the helper objects and the client call for engine_newPayloadV4.

Fixed Issue(s)

part of #8620

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.

[StefanBratanov]

LGTM. I would just remove .getMilestone now from ExecutionPayload to avoid it getting misused.

[lucassaldanha]

LGTM. I would just remove .getMilestone now from ExecutionPayload to avoid it getting misused.

Will do on the follow up PR 👍