Support legacy blocks/transactions information

[shuse2]

LIP

As recommended in the Migration LIP, it would be helpful if we keep the Lisk Core v3 Block History and we can generalise it for the future hard forks too.

Motivation

After migration, blocks and transactions from the pre-migration chain should be stored on a node and possible to provide through endpoint

Tasks

• Bootstrap legacy chain handler related files and folders #7481
• Implement all storage related functions to handle blocks for SDKv5 #7482
• Implement all data access related functions to handle blocks for SDKv5 #7483
• Implement methods for LegacyChainHandler to expose data access #7484
• Add validation logic for blocks and transaction root #7504
• Implement syncBlocks function of LegacyChainHandler #7486
• Implement syncHandler for handling getLegacyBlocksFromId RPC #7487
• Expose endpoints for legacy under endpoints in engine #7488
• Add legacy property on nodeInfo to be shared to peers #7498
• Add config for legacy that stores brackets #7499
• Register endpoints and handlers for legacy #7485
• Integrate legacy chain handler with application #7501
• Manage node to sync legacy blocks in the start of the node #7503
• Implement sync method on LegacyChainHandler #7547
• Define storage for saving info about legacy chain brackets #7545