feat: fetch gasless transactions for BatchSell quotes

[micaelae]

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
Adds a new network call and state lifecycle for fetching gasless BatchSell transaction batches/fees, plus a breaking selector output change that clients must adapt to. Risk is mainly around request cancellation/ordering and fee display correctness based on the new API response validation.

Overview
Adds a new BridgeController:fetchBatchSellTrades action that calls the bridge API obtainGaslessBatch endpoint, storing the resulting transaction batch + fee data in new state fields (batchSellTrades, batchSellTradesLoadingStatus) with abort-on-refresh/reset behavior.

Introduces selectBatchSellTrades (and fee conversion via calcBatchFees) to surface the batch transactions and a converted totalNetworkFee, and removes totalNetworkFee from selectBatchSellQuotes (breaking consumer change).

Extends types/validators to model and validate the gasless batch response (including transaction type and hex gas fee limits), updates RequestStatus enum values, and expands unit/snapshot tests to cover fetch, abort, and error/reset cases.

^{Reviewed by Cursor Bugbot for commit bb9931b. Bugbot is set up for automated code reviews on this repo. 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.}

^{Reviewed by Cursor Bugbot for commit bb9931b. Configure here.}

[cursor]

Aborted fetch unconditionally clears valid batch trade data

Low Severity

In fetchBatchSellTrades, the catch block unconditionally resets batchSellTrades to null before checking if the error is an abort. If two calls overlap and the newer one resolves before the older one's abort-triggered catch runs, the catch will overwrite the valid batchSellTrades result with null, leaving the state showing batchSellTradesLoadingStatus: FETCHED with batchSellTrades: null.

 

^{Reviewed by Cursor Bugbot for commit bb9931b. Configure here.}