Successful execution preconfs and use cases using `receipts_root`

[thedevbirb]

For inclusion preconfirmations we're leveraging the transactions_root field of the execution block header along with Merkle proofs. In order to prove successful execution of a transaction (or a bundle) we could do the same but with the receipts_root of the receipt MPT. The flow will look as follows:

• Users ask for transaction inclusion with successful execution
• Proposer signs commitments and those get propagated up to the builder level
• The builder provides Merkle proof of inclusion of the transaction at index i (it is already like this) along with the i-th receipt data and a MPT Merkle proof of inclusion
• The proposer then checks that both proofs are valid and that the receipts data shows a successful execution.

The receipt also contains all the logs emitted by the transaction. We should explore what use cases this unlocks!

[merklefruit]

Tentative tasklist to get this done in our devnet:

• [ ] spec out the constraints and commitments API changes for this type of commitment
• [ ] add an MPT Solidity library with capability to verify a merkle proof
• [ ] builder: generate the MPT receipt proof during the block sealing process
• [ ] implement API changes in the builder
• [ ] implement API changes in the relay
• [ ] implement API changes in bolt-sidecar

Note that this would still be a naive implementation, because the block building algorithm would need to be modified to include this type of transaction (avoiding for it to revert if possible).