## Description 

a separate pruner that use `epochs` table and `cp_tx` table to track
progress of pruning and handle disaster recovery;
and `checkpoints` table as available range data source.

## Test plan 

local run and verify via local client
- progress tracking via epoch, cp, and tx

![epoch_progress](https://github.com/MystenLabs/sui/assets/106119108/f628c7b5-add7-4198-94e3-f2542dfd7890)

![tx_cp_progress](https://github.com/MystenLabs/sui/assets/106119108/4395ff7d-b79b-4a6d-aec6-243ac5c86c22)



- verify on checkpoints & tx_ tables
  - make sure that the checkpoints table is indeed latest cp_tx cp + 1

![check_cp](https://github.com/MystenLabs/sui/assets/106119108/13de7129-16b6-44e9-a922-c487100cb152)
  - make sure that all cp < min_tx in cp_tx have been pruned

![check_tx](https://github.com/MystenLabs/sui/assets/106119108/0708e667-135a-44be-be77-b1eb667ba640)

---



## Release notes

Check each box that your changes affect. If none of the boxes relate to
your changes, release notes aren't required.

For each box you select, include information after the relevant heading
that describes the impact of your changes that a user might notice and
any actions they must take to implement updates.

- [ ] Protocol: 
- [ ] Nodes (Validators and Full nodes): 
- [ ] Indexer: 
- [ ] JSON-RPC: 
- [ ] GraphQL: 
- [ ] CLI: 
- [ ] Rust SDK: