Describe the feature

EIP-7742 moves blob target/max outside of EL and into CL only. These parameters are then posted over engine API. For historical sync, these fields are present in the header.

The target/max should be propagated from the engine API and into payload building. Any reference to the hardcoded 3 target should be replaced with the new dynamic value, and any reference to the 6 max should be replaced with a new dynamic value.

See https://eips.ethereum.org/EIPS/eip-7742, specifically

Upon activating this EIP (i.e. before processing any transactions), the verification of the blob maximum as given in EIP-4844 can be skipped. Concretely, this means any logic relating to MAX_BLOB_GAS_PER_BLOCK as given in EIP-4844 can be deprecated. Additionally, any reference to TARGET_BLOB_GAS_PER_BLOCK from EIP-4844 can be derived by taking the target_blobs_per_block from the CL and multiplying by GAS_PER_BLOB as given in EIP-4844.

It is important that this does not affect Optimism (and Odyssey), namely the fields should not be required to be in the block header even if Prague is activated if we are running Optimism.

Additional context

No response