Etherlink/Revm: use the tx env builder to auto-derive the transaction type

Context

We use a proper transaction env. builder to help auto-deriving the transaction type. Otherwise for transaction with access list (EIP-2930) the list isn't taken into account. Same would of happen with other tx-type specific fiels.

Testing

Trigger the following test with and without the patch:

dune exec etherlink/tezt/tests/main.exe -- evm eip2930 /dal /multichain_enabled alpha latest --file evm_sequencer.ml --verbose

MR-chain

Prev: !18634 (merged)

Next: !18624 (merged)