[Feature] Enforce request structure during deserde

[mattsse]

Component

consensus, eips, genesis

Describe the feature you would like

executionRequests: Array of DATA - List of execution layer triggered requests. Each list element is a requests byte array as defined by EIP-7685. The first byte of each element is the request_type and the remaining bytes are the request_data. Elements of the list MUST be ordered by request_type in ascending order. Elements with empty request_data MUST be excluded from the list.

we currently don't enforce:

• ordering
• length

alloy/crates/eips/src/eip7685.rs

Lines 21 to 22 in d414596

	#[cfg_attr(feature = "serde", derive(serde::Serialize, serde::Deserialize))]
	pub struct Requests(Vec<Bytes>);

ordering could either be enforced in deserde or in request_hash #1871

if we do it in deserde then the consumer must ensure the requests are pushed in order

https://github.com/ethereum/execution-apis/blob/main/src/engine/prague.md#engine_newpayloadv4

Additional context

No response

[nadtech-hub]

✋

[mattsse]

we now have the proper checks in place so we no longer need this