Etherlink: reconstruct option in init from rollup node

What

Allows to reconstruct the history.

Why and how

To request intermediate states of the chain. We regularly renitinialized the state of the evm-node using init from rollup node on ghostnet, it's convenient because all the blocks are stored in the durable storage. However, when you initialize from a rollup node, you only have one irmin commit, therefore you can requests info about the latest evm state only. As long as the ""network"" is willing to store the blueprints and share them this merge request is not needed, the alternative is to ask the blueprint starting from 0. The reconstruct I'm proposing here relies only on the smart rollup add messages, which is published to L1 and therefore we have the full history in the worst case.

The behavior is fairly simple: execute all messages since the origination. Therefore it requires an archive node, it could be generalised to use the first_available_level of a rolling node.

Manually testing the MR

Checklist

• Document the interface of any function added or modified (see the coding guidelines)
• Document any change to the user interface, including configuration parameters (see node configuration)
• Provide automatic testing (see the testing guide).
• For new features and bug fixes, add an item in the appropriate changelog (docs/protocols/alpha.rst for the protocol and the environment, CHANGES.rst at the root of the repository for everything else).
• Select suitable reviewers using the Reviewers field below.
• Select as Assignee the next person who should take action on that MR