fix(assets-controller): hardened error handling

[Kriys94]

Explanation

References

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

---

Note

Medium Risk
Changes token metadata and spot-price fetching to chunk and parallelize API calls, which can affect request volume/ordering and backend rate limits. Also wraps several polling/update callbacks to prevent unhandled exceptions, reducing crash risk but potentially masking bugs behind logs.

Overview
Improves assets pipeline robustness by preventing unhandled exceptions in several async update paths: wraps onActiveChainsUpdated handling in AssetsController, and guards RpcDataSource balance/detection polling callbacks plus StakedBalanceDataSource polling callback so failures are logged instead of rejecting poll ticks.

Updates token/price enrichment to respect v3 API asset ID limits: TokenDataSource and PriceDataSource now split requests into chunks of max 120 IDs and execute chunk fetches in parallel with bounded concurrency via p-limit (including dual-currency price fetches). Adds coverage to verify chunking behavior, and hardens SnapDataSource against missing/undefined balances payload fields.

^{Written by Cursor Bugbot for commit 01c36b2. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

[cursor]

Non-USD price fetches serialized instead of parallel

Medium Severity

For non-USD users, the old code ran selected-currency and USD fetchV3SpotPrices calls in parallel via Promise.all. The new code fully awaits all selected-currency chunk results before starting any USD chunk requests, serializing what was previously parallel. Since the pLimit instance is shared, both sets of chunks could safely be dispatched together through the same limiter. For the common case (≤120 assets, single chunk per currency), this roughly doubles the price-fetch latency on every poll tick for all non-USD users.