[Neo Plugin UT] Add a dbft unit test system

[Jim8y]

Description

DBFT plugin lacks unit test system. Thus having this pr that build a unit test environment for DBFT plugin.

This UT will mock a 7 nodes network.

Problem still exist in this test engine that consensus will still go automatically, we need a manual system where every single nodes operation can be manually controlled and set. But it should be fine since test is not likly run over 15s.

Fixes # #3231

Type of change

• Optimization (the change is only an optimization)
• Style (the change is only a code style for better maintenance or standard purpose)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Test Configuration:

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[shargon]

if debug?

[vncoelho]

I understand the test but this is a little different from what we had before.
The AkkaTestkit was used to simulate the calls.

Consensus tests need to be something that we can call the same methods and flow of the consensus, such as Reset, InitializeConsensus, MakePrepare Request,etc...

Maybe your way is even better, but this is not clear to me yet.
So, for now I would prefer to merge in another branch until we extend the tests for at least a simple flow of the consensus. Then, we add other possible scenarios.

[Jim8y]

I understand the test but this is a little different from what we had before. The AkkaTestkit was used to simulate the calls.

Consensus tests need to be something that we can call the same methods and flow of the consensus, such as Reset, InitializeConsensus, MakePrepare Request,etc...

Maybe your way is even better, but this is not clear to me yet. So, for now I would prefer to merge in another branch until we extend the tests for at least a simple flow of the consensus. Then, we add other possible scenarios.

I will keep updating according to your suggestion, not necessarily be one way, i will also add the method you mentioned.

[vncoelho]

I understand the test but this is a little different from what we had before. The AkkaTestkit was used to simulate the calls.

Consensus tests need to be something that we can call the same methods and flow of the consensus, such as Reset, InitializeConsensus, MakePrepare Request,etc...

Maybe your way is even better, but this is not clear to me yet. So, for now I would prefer to merge in another branch until we extend the tests for at least a simple flow of the consensus. Then, we add other possible scenarios.

I will keep updating according to your suggestion, not necessarily be one way, i will also add the method you mentioned.

Great, let me know because I am available to help as soon as I understand the way you are designing for calling these methods.