feat: query transactions on networks independently

[MuckT]

Description

Alternative implementation of #5432 which addresses the comments raised in #5432 (comment) passing state and setState to the queryTransactionsFeed function.

Test plan

• Tested locally on iOS
• Tested locally on Android
• Unit tests updated

Related issues

• Fixes ACT-1186

Backwards compatibility

Yes

Network scalability

If a new NetworkId and/or Network are added in the future, the changes in this PR will:

• Continue to work without code changes, OR trigger a compilation error (guaranteeing we find it when a new network is added)

[codecov]

Codecov Report

Attention: Patch coverage is 93.10345% with 4 lines in your changes missing coverage. Please review.

Project coverage is 86.46%. Comparing base (8394ddd) to head (f22d0d9).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5528   +/-   ##
=======================================
  Coverage   86.46%   86.46%           
=======================================
  Files         762      762           
  Lines       31456    31481   +25     
  Branches     5422     5427    +5     
=======================================
+ Hits        27197    27219   +22     
- Misses       4028     4031    +3     
  Partials      231      231           

Files	Coverage Δ
src/transactions/feed/queryHelper.ts	93.45% <93.10%> (-1.66%)	⬇️

... and 1 file with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8394ddd...f22d0d9. Read the comment docs.

[jeanregisser]

Awesome! Thanks for working on this! 🚀

[jeanregisser]

I'm wondering if we could avoid that check and the need to pass setActiveRequests / activeRequests
Is the problem that useAsync can call queryTransactionsFeed multiple times, but we effectively only care about the last one?

[MuckT]

I added this because some slow networks, such as polygon, take longer than the polling interval to return a result, so we can end up with multiple pending requests that are slow to resolve.

[jeanregisser]

I wonder if we need to worry that this is handled only for the "current" promise of queryTransactionsFeed.

But maybe since the result is deduplicated it's fine?

[MuckT]

We also handle the pending states for polling and pagination separately so it should only fire one request of each type per network.