Implement Fast chain switching mechanism as per the specifications in Introduce BFT consensus protocol LIP

[SargeKhan]

Expected behavior

The Introduce BFT consensus protocol LIP introduces Fast chain switching mechanism. This functionality should be implemented in the framework.

Linked tasks:

• Implement mechanism for finding commonBlock Implement mechanism for finding commonBlock #3769
• Blocks need to be stored in temporary table on block deletion Blocks need to be stored in temporary table on block deletion #3772
• Blocks need to be restored from temporary table upon failure Blocks need to be restored from temporary table upon failure or application restart #3775
• Implement functionality for removing blocks stored in temp table Implement functionality for removing blocks stored in temp table #3776
• Blocks need to be restored from temporary table upon restart node Decide to restore blocks upon startup when temp_block table is not empty #4348
• Modify BSM logic for finding common block for FCS Implement finding common block for FCS #4337
• Query all blocks from common block for peer and validate for FCS Query all blocks from common block for peer and validate for FCS #4338
• Switch to different chain for FCS Switch to Different Chain via FCS #4339

Note for FCS: Forging is disabled during the whole process of moving to a different chain.

Actual behavior

The Fast chain switching mechanism is yet to be implemented in the framework.

Which version(s) does this affect? (Environment, OS, etc...)

3.0.0