Separate different features in polybft package to separate packages

[goran-ethernal]

Description

New packages in polybft

• blockchain - contains block_wrapper, block_builder logic.
• bridge - contains all the bridge logic.
• config - contains polybft config structures and helper functions used to save the polybft config to genesis file, and reading it.
• governance - contains all the governance logic.
• helper - contains helper functions used across the polybft packages.
• metrics - contains helper functions to increment different metrics in polybft.
• proposer - contains proposer_calculator and proposer_snapshot logic.
• stake - contains the stake_manager logic.
• state - contains the logic for creating db for saving different offchain data in polybft.
• system_state - contains all the systemState logic.
• testing - contains mocked structures.
• types - contains common polybft types used throughout polybft (for example, Extra).
• validator-snapshot - contains all the logic around validator snapshots.

What logic was changed

• all the packages that require a form of persistance store now have their own state_store file, and those stores are not initialized like before in the global state instance. Global state instance now only opens a db. The rest of the stores now use the db instance from the global state instance to initialize their buckets.
• mocks are now in the mocks package.
  The rest of the logic is basically the same, and was not changed.

How to review

Most of the changes are just package name changes. Only focus on the points in the previous section.

Changes include

• Bugfix (non-breaking change that solves an issue)
• Hotfix (change that solves an urgent issue, and requires immediate attention)
• New feature (non-breaking change that adds functionality)
• Breaking change (change that is not backwards-compatible and/or changes current functionality)

Checklist

• I have assigned this PR to myself
• I have added at least 1 reviewer
• I have added the relevant labels
• I have updated the official documentation
• I have added sufficient documentation in code

Testing

• I have tested this code with the official test suite
• I have tested this code manually