Lock chain before start mining

[Neylix]

Description

This PR adds a new security layer before to start mining a transaction.
When receiving the StartMining message for a transaction, validation nodes request the storage nodes of this transaction to lock the address. If the address is already locked for the same address but with a different transaction data, the lock is refused and the validation node does not start the mining.

This PR does not handle malicious node which could still start the transaction mining even with no lock. And so ask the replication to storage nodes.
To handle this, the storage nodes could sign the lock request, and so the storage nodes will replication the transaction only if they have the proof of the request lock being signed by all storage nodes.

Fixes #1373

Type of change

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

• Unit test
• Create multiple transaction in the same chain => no problem
• Create an invalid transaction send it and retry to validate it again after receiving the error => no problem, transaction still in error with the expected error
• Create an invalid transaction send it, update it and retry to validate it again after receiving the error => no problem, transaction still in error with the expected error
• Update the code so the node never unlock an address, and run the previous test => validation nodes return the error that the transaction is already locked with another data
• Tested with high usage with benchmark => no problem

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own 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