Quorum ibft to besu qbft migration

[pullurib]

PR description

Code Changes

• Restored the removed IBFT code required for parsing and validating IBFT extra data.
• Added test cases for importing IBFT blocks into a Besu network that transitions to QBFT after the imported IBFT blocks.
• Developed an end-to-end test case to simulate a 5-node Besu network and validate the block import process.

Initial Test Setup

Start a Quorum IBFT network with:

• 5 nodes.
• A genesis file that includes forks configured similarly to BaaS.
• Approximately 10 blocks for each fork.
• Add a few transactions to the network.

Allow the network to mine up to 100 blocks.

Start migration process on Test or Production Chains

• Stop 4 validators (to halt mining).
• Create a copy of the genesis file and update it to include a transition to QBFT from the block immediately following the latest block on the Quorum chain.

Export and Import

• Export all blocks from the Quorum chain to an RLP file.
• Copy the exported blocks RLP file, validator keys, and the updated genesis file to a corresponding Besu network with 5 nodes.
• Use the bootnode in the Besu network to import all blocks from the RLP file.
• Start the Besu network with all 5 nodes. Allow the remaining nodes to sync with the bootnode and begin mining QBFT blocks.
• Compare the latest block on both networks, verifying the state root, transaction root, and other relevant data.

Sync with Quorum Network

• Copy the genesis file and validator keys from one of the stopped Quorum validators to a Besu node.
• Configure the Quorum node as the bootnode in the Besu node’s configuration.
• Start the Besu node and verify that it syncs with the Quorum network.
• Stop the last Quorum node.
• Start 4 additional Besu nodes using the validator keys from the Quorum network.
• Confirm that the Besu QBFT network starts mining new blocks.
• Compare block 100 on both networks, ensuring that the state root, transaction root, and other metadata match.

Fixed Issue(s)