Configurable BlockNumber for View endorsement chain

[satz07]

Summary

What is the background of this pull request?
Change the from block number logic so that TradeTrust starts fetching from the block number when it was integrated into the XDC Network, instead from the genesis block. This will ensure faster and efficient responses.

Changes

• Added blockNumber field to chain info. It is an optional parameter for any chains to use.
• Updated the functions to use this blockNumber instead from the genesis block to query
• Updated the Integration tests with additional parameter

Issues

View endorsement chain during verification of document fails as it requires archival node to fetch complete history and fetches data from genesis block

[netlify]

👷 Deploy request for tradetrust-beta pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	aa55485

[netlify]

👷 Deploy request for reference-implementation pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	aa55485

[MinHtet-O]

Hi @satz07,

We are currently benchmarking and seeking opportunities to improve our view endorsement chain.

However, I am encountering inconsistent delays, way longer than usual, in some operations using the RPC URL provided by the XDC team. These inconsistencies make it difficult to compare the overall durations of the view endorsement chain before and after optimizations. Could the XDC team assist us by providing a stable RPC URL?

[MinHtet-O]

Regarding the changes in querying the blockchain starting from a specific block number, may I know in detail how much the view endorsement chain process on XDC improves? We need to determine if the cost of changing the code and adding extra complexity outweighs the efficiency gains. When I tested it on Sepolia, I did not see significant improvement.