Data Availability re-orgs handling tracking issue

[citizen-stig]

At present, the Sovereign SDK processes only finalized blocks. To enhance response times, the SDK should be equipped to manage re-organizations of the blockchain structure due to forks in underlying Data Availability(DA) layers.

Steps

• Update rollup-interface with notion of external storage: Extract storage creation from State Transition Function #1103
• Make DaService trait aware about re-ogranizations and finalization #1024
• Storage should support nested snapshots  #1026
  • Add snapshot support to sov-schema-db Add DbSnapshot to sov-db-schema #1112
  • K, V Iterator for DbSnapshot #1177
  • Crate for managing Storage snapshots relationship to DA forks  #1027
  • Integrating Nested Prover Storage Management #1197
• sov-stf-runner should handle DA head change. #1217
• RPC endpoint should point to head storage, instead of finalized storage #1218

Prerequisites:

• Removing Storage::backing method #978 as it leaks abstraction

Finalization and Refactoring

• Bug: Handle state root change in runner in case of re-org
• ProverStorageManager: wrapper struct for 3 RwLocks so they all written together.
• ChangeSet from default Stf should be a different type from PreState
• Remove explicit Arc<RwLock> from Blueprint and Runner and unify it with RpcStorage.
• Reexport jmt::RootHash & jmt::SparseMerkleProof from sov-state #1249
• Unify StorageKey and CacheKey #643 as less types will simplify the change
• Integrate the ProverService with the ForkManager #1185
• Refactor SchemaIterator so it utilizes already tested logic of RawDbIter
• Explore removing Mutex inside CacheDb and change API to have &mut self
• Optimize CacheDb for multithreaded execution.