Feature/exittree

[arnaubennassar]

• promoted localbridgesync to bridgesync since now it will sync both L1 & L2 bridges
• Separated the tree from the bridge processor, as now this tree will be reused by many syncers. Although the file appears to be new on the Files changed the logic is pretty much the same, just separated the tree
• Made the DB keys big endian as little endian had problems when sorting
• On the L1 Info tree sync:
  • Added verify batch events to the l1 info tree downloader, as those are needed to build the rollup exit tree
  • Modified the E2E test to use verify batches event (had to create a custom contract for that). Also added a stress test. The stress test has the capability of simulating reorgs, but this is disabled as the test is failing wen enabled, and this was outside the scope of the PR
  • The l1 info tree processor has replaced the l1infotree implementation for the new generic tree implementation
  • It also has added an instance of rollup exit tree
  • And simplified a lot the schema by removing the index and root tables
• On the evm downloader:
  • check that hash matches when querying block header from a log
  • filter logs, but not in the query since it can be problematic on some rpc providers
• added ctx on the Reorg and ProcessBlock functions for the processors
• Build a generic tree processor. This tree has two operational modes: append only and updatable. Note that both modes are tested through the l1infotreesync/e2e_test.go. Note that the AppendOnlyTree was used previously in the localbridgesync

[goran-ethernal]

Leaving some comments. Haven't finished reviewing appendable and updateable tree.

[goran-ethernal]

LGTM, but we have a UT failing. Might be good to check what is going on.

[sonarcloud]

Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 80%)
14.0% Duplication on New Code (required ≤ 3%)

See analysis details on SonarCloud