feat: send l1infotree data to the aggchain prover

[goran-ethernal]

Description

This PR implements the additional logic of sending l1infotree data to the aggchain prover that is needed to generate a aggchain (auth) proof.

The data includes:

• start block from which to build a proof.
• max end block to which a proof needs to be built.
• last finalized l1InfoTreeRoot.
• the leaf with the highest index on that block and given finalized l1infoTreeRoot.
• merkle proof of the given leaf on given root.

Based on the provided block range and on the finalized l1 info tree data we send to the prover, prover can either return the maximum block range we asked, or return a smaller range.

But, in order to do this, all the syncers need to store block hash as well to the block table. Before this PR, only l1infotreesyncer stored this data, but we might need it in all syncers (to be consistent), so this PR expanded all the syncers to store the block hash as well.

Fixes # (issue)

[joanestebanr]

Why is the reason that you need blockHash to all syncers? It looks like is not used on bridesync neither lastgersync.. isn't?

[goran-ethernal]

Why is the reason that you need blockHash to all syncers? It looks like is not used on bridesync neither lastgersync.. isn't?

To be consistent. It is useful for debugging, if we have issues on other syncers with reorg detection.

[sonarqubecloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

Measures
0 Security Hotspots
85.1% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud