Fix replication chain ingestion

[Neylix]

Description

There is some case where a node should replicate a transaction but it do not due to some latency or network issue. If there is a new transaction in this chain and the node is again storage node of this transaction, it will store the previous transaction without ingesting data as it should have been done.
This PR fix this problem by ingesting if needed the previous transaction of a chain

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