Fix get transaction chain lookup

[ghost]

Description

Fix the transaction chain reading to make sure the chain is one expected, so bigger.
Since d244b1d, the chain was downloaded using a diff between local and remote fetch.

The problem being, if a local chain was bigger than the address of the chain requested (pointer) we would include more transaction than expected. And also we might cause database issues, because the pagination address was the latest one, which don't provide much transactions to load.

This fix makes sure we only download the right transactions until the desired transaction's address.

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

[apoorv-2204]

LGTM