Implement Fix for Paging Limit and Large Block Retrieval

[quiet-node]

Description

Implement the necessary code and configuration changes to:

• Remove or raise the hard cap on the maximum number of transactions returned per block to align with network throughput thresholds.
• Considering Hedera’s ~10,000 TPS and a ~2-second block time, aim to support blocks with up to ~20,000 transactions.
• Ensure paging parameters (MIRROR_NODE_LIMIT_PARAM and MIRROR_NODE_CONTRACT_RESULTS_PG_MAX) reflect this higher cap and are properly handled by the Relay and Mirror Node.
• Enable full retrieval of blocks with large transaction volumes, including synthetic HTS transactions, without errors.

Goals

• Unblock retrieval of large blocks exceeding the current 2,500 transaction cap.
• Align paging limits with the expected maximum network transaction volume per block.
• Preserve system stability and avoid performance regressions during implementation.

Deliverables

• Code and configuration updates in Relay and Mirror Node.
• Updated documentation reflecting new paging limit parameters and expected block sizes.
• Unit and integration tests verifying retrieval of large blocks without errors.
• Coordination plan for follow-up performance testing and optimization.

Acceptance Criteria

• Blocks with transaction counts up to the new cap (e.g., ~20,000) can be retrieved fully without paging errors.
• Paging logic correctly supports the increased limits.
• No regressions or instability are introduced.
• Performance testing is planned post-implementation.