Modules to depend on storage layers instead of database operation functions

[zhangchiqing]

Context

We have many places read and write data with database operation functions directly. This direct dependencies on the badger-based operation functions make it hard to implement the following features, since the data might store in different database:

1. badger -> pebble migration
2. implement pruning for regisiter DB or chunk data pack DB.

Proposed Solution

It's better for the modules to depend on the storage interfaces instead of database-specific operation functions, so that by using different storage implementation, it knows how to do the same operation for different databases.

TODO

Update modules that uses database operation functions to use storage interface methods.

cc @peterargue

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.