Feature/1870 historic state rotation

[olehnikolaiev]

fixes #1870

introduce rotating historic state - skaled writes to a historic db until its size less than HISTORIC_STATE_DB_LIMIT_BYTES bytes. then skaled closes that db for write and opens another one.

• Added BatchedRotatingHistoricDbIO class to manage the new historic state architecture. It rotates the databases, closes the dbs that are opend but not used and allow access to the specific db by block number.
• Added RotatingHistoricState class to access historic state db. It rotates the database pieces, performs read, write, add and delete operations through the element of BatchedRotatingHistoricDbIO class.
• Added rootBlockNumber parameter to the TrieDB for optimized scan of DBs in BatchedRotatingHistoricDbIO.
• MemoryDB and libdevcore/OverlayDB are merged together and stored under libskaled/OverlayDB directory in ClassicOverlayDB class.
• Skaled checks whether the historic state db needs to be rotated before executing block.
• BatchedRotatingHistoricDbIO allows to have up to MAX_OPENED_DB_COUNT open dbs at the same time. Any db might be open for up to OPENED_DB_CHECK_INTERVAL ms. Once one of these limits is reached skaled closes all dbs that are open but not in use. This is done to avoid huge resource consummation.

tests - added unit tests for the new historic state mechanism. tested it on the mainnet - spun up a Nebula Archive node and verified that it catches up blocks faster than they are produced.

docs: https://github.com/skalenetwork/internal-support/blob/main/docs/specifications/skaled/rotating-historic-state.md

[github-actions]

CLA Assistant Lite bot:
Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

_{You can retrigger this bot by commenting recheck in this Pull Request}

[github-actions]

SUGGESTIONS BEFORE MERGE:

1. Build custom container here: https://github.com/skalenetwork/skaled/actions?query=workflow%3A%22Custom+Docker+and+Binary%22
2. Test it here: https://github.com/skalenetwork/skale-ci-integration_tests/actions?query=workflow%3A%22Skaled+Nightly+Tests%22
3. Edit VERSION file appropriately to your changes!
   See https://skalelabs.atlassian.net/wiki/spaces/SKALE/pages/2444951553/Branching+instructions