feat: Trusted Builder Optimistic Simulation

[bharath-123]

Summary

This PR adds support to optimistically simulate bundles in composer. At a high level, we receive sequence actions from process_proposal and simulate the bundle on top of the received sequence actions. This allows us to stay in sync with conductor and gives us more time to submit the simulated bundle.

Background

A Trusted Builder is a sophisticated rollup entity who is responsible for creating high value bundles. Composer is part of the trusted builder. The trusted builder's composer is responsible for simulating the bundle created by the builder and removing any invalid or reverting txs. To achieve this, we have made changes to the ExecuteBlock method/ to have a simulateOnly mode and to return txs that have been successfully included in a block.

More details on Trusted Builder are included in https://www.notion.so/astria-org/Trusted-Block-Builder-MVP-8eba7cd7cbd34e4e90a4adf726879028?pvs=4

One of the key issues, we have observed in the first iteration of trusted builder was that the time taken to simulation and then to submit the transaction was not enough to ensure that our simulated bundle is applied on the parent hash on top of which it was simulated.

To avoid this, we modify sequencer to push sequence actions which are being processed to the composer. We simulate the bundle on top of these sequence actions. We also modify sequencer to push the finalized block hash, we only submit the simulated bundle if this finalized block hash matches the block hash of the sequence actions submitted during process_proposal.

More details on the iterations are listed at: https://app.excalidraw.com/s/11QAdJyeldV/A3su0PdTwsU

Changes

• Add a BundleBuilderPacket proto which is the artifact containing the simulated sequence actions and the parent hash on top of which we have simulated the sequence actions.
• Add a SendOptimisticBlockRequest proto which contains the sequence actions sequencer pushes to composer during a process_proposal.
• Add a SendFinalizedBlockHashRequest proto which contains the finalized block hash sequencer pushes to composer during finalize_block
• A grpc client to interact with Execution API (This is copied from conductor)
• Creating of the parent block(i.e the sequence actions received from sequencer in SendOptimisticBlockRequest) and simulation of bundle on top of the parent block hash.
• Add logic in sequencer to push sequence actions in process_block to composer via the SendOptimisticBlockRequest request.
• Add logic in sequence to push the finalized block hash in finalize_block to composer via SendFinalizedBlockHash request.

Testing

• By deploying it locally and running spamooor against it.

Breaking Changelist

• Bulleted list of breaking changes, any notes on migration. Delete section if none.

closes

[bharath-123]

maxBundleSize can be removed.

[bharath-123]

This is not necessary, we can just hard code this in the binary.