Enhancement/skaled 1583 patch architecture

[dimalit]

fixes #1583

Description

1. "Forks" are now activated by block timestamp, rather than number.
2. There are DEFINE_XXX_PATCH macros for defining patches.
3. Timestamps for patches are automatically read from config.
4. Existing patches use these macros.

Tests

Tests for patches:

• ContractStorageLimitPatch: storage_limit_reverted
• ContractStorageZeroValuePatch: tested manually, used in test storage_limit_predeployed
• RevertableFSPatch: FilestorageCacheSuite)
• StorageDestructionPatch: tested manually with JsonRpcSuite/simple_contract
• POWCheckPatch: powTxnGasLimit
• PushZeroPatch: LegacyVMSuite/InstructionSuite
• SkipInvalidTransactionsPatch: SkaleHostSuite
• PrecompiledConfigPatch: PrecompiledTests/getConfigVariable
• CorrectForkInPowPatch: simplePoWTransaction
• VerifyDaSigsPatch - need to check manually!

Performance Impact

There can be significant performance impact, as patch activations are evaluated at each block or sometimes even every transaction. This is to be tested separately

Details about changes in code

1. A lot of functions that needed only blockNumber parameter now need also committedBlockTimestamp.
2. Removed 'Frontier' fork (it was never used), as well as 'SkaleNNNForkBlock`s for same reson.
3. EVMSchedule can now be constructed from several patches, and not only taken from pre-defined list as before (ChainOperationParams::evmSchedule)
4. Some functionality moved from SealEngine to ChainOperationParams, and SealEngine is now unneeded in some places, where ChainOperationParams suffice - for simplification of architecture. Also it's planned to cut out SealEngine completely.
5. PushZeroPatch uses boolean field in EVMSchedule, and generates new EVMSchedule similar to 'fork blocks'
6. In libethereum/SchainPatch.h there are new macros for creation of patches.
7. Almost all old patches now use these macros (see SchainPatch.h)
8. Latest block timestamp is updated every block for all patches at once - in SchainPatch class.

[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

[dimalit]

Superseded by #1868