Replace Badger with Pebble DB - Execution data

[j1010001]

Why

In general, see Epic: #6515

**Specifically for this issue: **
Subset of Execution data gets indexed on ANs (events, Txs, Tx results, collections (meta object on top of Tx) ⇒ data that gets pulled out of execution data blobs).
ANs are the biggest data-heavy node after EN, expecting to grow further with EVM equivalence. By enabling data pruning we enable them to run AN with index on lower spec HW.

Current status

• Execution data is stored in Badger DB.
• @zhangchiqing abstracted the DB access in [Badger] Add universal database operations #6465, which makes it easier to swap the DBs in the future - this work depends on it. (Usage example: [Badger] Refactor approvals to use badger batch updates #6466)

How will we measure success ?

• Access and Execution nodes are able to automatically prune it's execution-data.
• Access node removes dependency on Badger DB

Estimate

4 dev/weeks to be ready to deploy.

DACI

TBD

Tasks

Beta Give feedback

1. Replace Badger Transaction with Batch updates - Access Node-related data #6518
   +0
2. Replace Badger Transaction with Batch updates - Verification Node-related data #6519
   +0
3. Replace Badger Transaction with Batch updates - Execution Node-related data #6520
   +0