Badger -> Pebble DB M3: unblock pruning of Execution, Access and Verification data

[j1010001]

Note: ideally we use the locking framework as proposed in: https://github.com/jordanschalm/lockctx/blob/main/README.md Completing this milestone enables removal of dependency on Badger DB from Verification node.

Follower @zhangchiqing

• [ ] Execution https://github.com/onflow/flow-go/pull/7262
• [ ] Verification https://github.com/onflow/flow-go/pull/7262
• [ ] Access https://github.com/onflow/flow-go/pull/7262
• [ ] Collection https://github.com/onflow/flow-go/pull/7262

Common to all nodes - needed for completing DB migration to Pebble

• [x] Libp2p Blocklist @fxamacker https://github.com/onflow/flow-go/pull/7361

Added scope (end of Apr) Follower:

• [ ] Consensus Builder https://github.com/onflow/flow-go/pull/7262
• [ ] Finalizer https://github.com/onflow/flow-go/pull/7262

Other:

• [x] Persister https://github.com/onflow/flow-go/pull/7358

• [x] ExecForkSuppressor - add evidence of error conditions to Pebble (@fxamacker ) https://github.com/onflow/flow-go/pull/7388

• [ ] Deployment - Switching from Badger to Pebble (Dynamic bootstrap (preferred), spork, or Migration) https://github.com/onflow/flow-go/issues/7395

• [ ] Protocol Data (Consensus Follower) https://github.com/onflow/flow-go/pull/7262

• [ ] Documentation: https://github.com/onflow/flow-go/issues/7397

[fxamacker]

This item Libp2p Blocklist was completed by:

• #7361
• #7363

[j1010001]

code complete, closing pending code reviews for follower engine. Does not cover the code to perform the actual pruning, just gets the data in Pebble to enable pruning.

[zhangchiqing]

Closed by https://github.com/onflow/flow-go/pull/7794