1850 historic node reset db

[kladkogex]

The problem was that MANIFEST file of historic state LevelDB was growing indefinitely.

Since during restart MANIFEST file is read and processed, it led to extremely long opening times.

1. A new config parameter has been added

leveldbReopenIntervalMs

The default value of leveldbReopenIntervalMs is one day or 24 * 60 * 60 * 1000 microseconds.

If leveldbReopenIntervalMs is negative (like -1) than the features is disabled

2. Everytime there is a write batch to LevelDB (this typically happens after block processing) there is a check for the
   age of LevelDB descriptor. If the descriptor age is more than leveldbReopenIntervalMs, the descriptor is closed and opened again.

3. Reopen of the descriptor happens while holding write lock (inclusive lock) Use of the descriptor happens while holding read lock.

4. A new test infinite_loop_test is used to test the functionality. During the test, transactions are generated in the blockchain, while leveldbReopenIntervalMsis set to 1ms. Manifest file of leveldb is observed to see that it does not grow.

5. Also readability of github tests were improved by adding --report_level=detailed options to testheth.
   Now if one of test_eth tests fails, it is way faster to understand which test fails and get the error message

[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