feat(tests,execute): expand 4844 test suite to use real blobs in execute mode

[marioevz]

          > test suite that sends blob txs to ELs, then we call `get_blobs` to validate the response. This feels suited towards an extension in `execute`.

This could even replace most of hive simulator tests if possible. The main issue right now is that most of the time we don't have full blobs in our tests but we only put the versioned hashes in the transaction. But perhaps we could put full blobs in the test transactions if we are running in execute mode (we could create a "mode" fixture that is populated with "fill" or "execute" depending on the pytest plugin).

Originally posted by @marioevz in #1510 (comment)

[marioevz]

Just to expand on this, I think we need to generate some real blobs using random data and then use ckzg to generate real proofs as @jtraglia suggested.

In the 4844 tests we simply use a hash with all zeros and a number at the end in place of real versioned blob hashes:

execution-spec-tests/tests/cancun/eip4844_blobs/test_blob_txs.py

Lines 103 to 116 in b33ed11

	@pytest.fixture
	def blob_hashes_per_tx(blobs_per_tx: List[int]) -> List[List[Hash]]:
	"""
	Produce the list of blob hashes that are sent during the test.
	Can be overloaded by a test case to provide a custom list of blob hashes.
	"""
	return [
	add_kzg_version(
	[Hash(x) for x in range(blob_count)],
	Spec.BLOB_COMMITMENT_VERSION_KZG,
	)
	for blob_count in blobs_per_tx
	]

This is ok for filled tests because the transactions in the blocks that are verified by these tests never contain the full blobs, so it does not matter that the versioned hashes do not correctly map to a real blob.

For execute we actually skip tests that use type-3 transactions because of this reason.

If we generate the tests with full blobs, even if the full blob never makes it into the filled test, we could use this full blob during execute and validate using getBlobs.

We have also to take into consideration this file:
https://github.com/ethereum/execution-spec-tests/blob/main/tests/cancun/eip4844_blobs/test_blob_txs_full.py

And this definition:

execution-spec-tests/src/ethereum_test_types/types.py

Lines 1073 to 1094 in b33ed11

	class NetworkWrappedTransaction(CamelModel, RLPSerializable):
	"""
	Network wrapped transaction as defined in
	[EIP-4844](https://eips.ethereum.org/EIPS/eip-4844#networking).
	"""
	tx: Transaction
	blobs: Sequence[Bytes] | None = Field(None, exclude=True)
	blob_kzg_commitments: Sequence[Bytes] | None = Field(None, exclude=True)
	blob_kzg_proofs: Sequence[Bytes] | None = Field(None, exclude=True)
	rlp_fields: ClassVar[List[str]] = ["tx", "blobs", "blob_kzg_commitments", "blob_kzg_proofs"]
	def get_rlp_prefix(self) -> bytes:
	"""
	Return the transaction type as bytes to be appended at the beginning of the
	serialized transaction if type is not 0.
	"""
	if self.tx.ty > 0:
	return bytes([self.tx.ty])
	return b""

Maybe moving blobs, blob_kzg_commitments and blob_kzg_proofs from NetworkWrappedTransaction back to Transaction so they are always accessible, and then execute (and https://github.com/ethereum/execution-spec-tests/blob/main/tests/cancun/eip4844_blobs/test_blob_txs_full.py) wrap the tx in NetworkWrappedTransactionfor their respective purposes.

@felix314159 @spencer-tb