Replicate previous chain raise on missed tx

[Neylix]

Description

During replication, if a node has to sync previous transactions of a chain, when it downloads them it ensure all transactions are fetched from the paging address to the limit address.
It ensure all transactions using there previous address which should be the address of the previous transaction fetched.

Fixes #1563

Type of change

• Bug fix (non-breaking change which fixes an issue)

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

[samuelmanzanera]

LGTM

[samuelmanzanera]

I'm wondering if we can even improve the security of this flow, by checking the proof of integrity of the transaction chain in the stream processing.

[Neylix]

I'm wondering if we can even improve the security of this flow, by checking the proof of integrity of the transaction chain in the stream processing.

As discussed, we are planning to evolve the proof of integrity so that it can be validated without the need of the previous transaction data. Combined with the proof of validation using BLS signatures, all the proofs could be validated in the message request before entering the replication process.