[Storage] Introduce support for namespace in state store

[sitalkedia]

Motivation

First PR for introducing fine-grained state storage support. This diff introduces a concept of namespace in the state store - with only account blob based namespace support to start with. The key to the state store for a namespace object can be namespace_+ rawkey. This way we can support different namespace objects within the same state store with the guarantee that there will not be any key collision. In order to support this, all account related concept has been moved out of the storage layer and instead the storage layer majorly understands the concept of StateStoreKey and StateStoreValue, which are arbitrary byte arrays. Please note that this is a major format change on the storage side and is not backward compatible - we need to wipe out the previous data from dev-net before rolling this out.

The diff touches many files because of the extensive API change, however, important changes to be reviewed at

types/src/state_store/state_store_key.rs
types/src/state_store/state_store_value.rs
storage/storage-interface/src/state_view.rs
storage/aptosdb/src/state_store/mod.rs
execution/executor/src/components/apply_chunk_output.rs

Test Plan

Modified existing UTs for new API interface.

[netlify]

✅ Deploy Preview for aptos-developer-docs canceled.

Name	Link
🔨 Latest commit	90646f5
🔍 Latest deploy log	https://app.netlify.com/sites/aptos-developer-docs/deploys/6242971c2a3c4500095f1b35

[sitalkedia]

/canary

[aptos-bot]

💔 Test Failed - build-test-deploy

[sitalkedia]

/canary

[sitalkedia]

/canary

[aptos-bot]

This PR is already being canaried

[aptos-bot]

💔 Test Failed - build-test-deploy

[sitalkedia]

/canary

[aptos-bot]

Forge run: https://circleci.com/gh/aptos-labs/aptos-core/5977
Forge Test Result: all up : 1966 TPS, 2236 ms latency, 3400 ms p99 latency,no expired txns

[aptos-bot]

💔 Test Failed - build-test-deploy

[sitalkedia]

/canary

[aptos-bot]

Forge run: https://circleci.com/gh/aptos-labs/aptos-core/5983
Forge Test Result: all up : 1858 TPS, 2353 ms latency, 3300 ms p99 latency,no expired txns

[aptos-bot]

💔 Test Failed - build-test-deploy

[sitalkedia]

/canary

[aptos-bot]

Forge run: https://circleci.com/gh/aptos-labs/aptos-core/6238
Forge Test Result: all up : 1801 TPS, 2430 ms latency, 5100 ms p99 latency,no expired txns

[sitalkedia]

@msmouse - I checked the failed tests and it seems like these are due to the new hash value of the keys creating different number of intermediate nodes as compared to the previous hashing scheme, I have updated the test. Please let me know your thoughts - cacb3f2

[sitalkedia]

/canary

[msmouse]

@sitalkedia Makes sense! (And it's a tricky one!)

[msmouse]

I think we can squash the two commits before landing this one.

[aptos-bot]

Forge run: https://circleci.com/gh/aptos-labs/aptos-core/6268
Forge Test Result: all up : 1936 TPS, 2269 ms latency, 3150 ms p99 latency,no expired txns

[aptos-bot]

☀️ Canary successful

[sitalkedia]

/land

[aptos-bot]

🔒 Merge Conflict

[sitalkedia]

/land

[aptos-bot]

Forge run: https://circleci.com/gh/aptos-labs/aptos-core/6300
Forge Test Result: Forge test runner is terminated

[aptos-bot]

Forge run: https://circleci.com/gh/aptos-labs/aptos-core/6306
Forge Test Result: ``