Enable plugins to provide Besu with a tracer

[OlivierBBB]

Description

To connect Linea's traces to the Shomei traces in Linea's state manager the most natural solution would be for the tracer plugin to be able to provide Besu with the Trie Logs it produced while executing a (sequence of) block(s).

The underlying issue is that the state accesses required by the arithmetization outnumber those produced by a normal Besu node. If the state accesses of the tracer plugin could be fed back to the trie logs that Shomei converts into its traces, we would solve this issue elegantly and at very small cost (as compared to a spec change.)

[matkt]

We want to allow the plugin to influence the generation of the Besu trielog for Shomei. Currently, when a read is done through a operation tracer, it already has some influence on the Bonsai accumulator because a read causes the data to be cached. The accumulator then takes everything in the cache to generate the trielog.

On Ethereum mainnet, a read doesn't end up in the trielog only updates do. But on Linea, reads are also included in the trielog for Shomei.

Right now, Besu’s trielog lacks certain information needed by Linea, and so some data is missing in the Shomei trace. This happens because Besu only reads what's required for execution, so some reads are missing from the trielog. However, the tracer plugin does read the missing data.

The idea is to allow the plugin to add its own operation tracer during block execution so that missing reads are also triggered, making the trielog complete.

There’s another aspect: Besu's trielog contains some reads that are necessary for Besu but not useful for Linea. So we also need to clean up those parts. The plan is to provide the plugin with an event after the block execution ends, so it can inspect the accumulator and remove any unnecessary entries before the trielog is generated.

This ticket is about updating the Besu plugin API. There are four main steps, two of which need to be done on the Besu side:

• Add a mechanism in the plugin API that allows a plugin to provide an OperationTracer during block execution. Currently, when Besu follows the head and imports a block, it’s not possible to inject a tracer from a plugin. We need to add this capability.

• Allow Besu to notify the plugin after all transactions have been executed, but before the state root is calculated something like an "all-transactions-executed" event.

  There will then be two additional changes required on the plugin tracer side (make sur the read are done in the plugin and keep track of the needed read in order to clean the accumulator at the end of the block)

[fab-10]

A plugin already has a way to define a tracer to be used during block creation, so this seems a similar requirement.
TransactionSelectionService can be used by a plugin to register a PluginTransactionSelectorFactory, that returns an implementation of PluginTransactionSelector, that behind other method can return an operation tracer that is used during block creation