feat: fetch gasless transactions for BatchSell quotes

[micaelae]

Explanation

Implements the updateBatchSellTrades handler which calls the obtainGaslessBatch to estimate network fees for BatchSell quotes. Clients will need to call the handler whenever the selectBatchQuotes selector's recommended quotes change

A new selector selectBatchSellTrades has also been added, which returns whether a batch is submittable, and the totalNetworkFee provided by the obtainGaslessBatch endpoint and its converted values

References

Fixes https://consensyssoftware.atlassian.net/browse/SWAPS-4444

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 async fetch path and state for BatchSell gasless trade/fee data, including abort/error handling and new API response validation. Risk is moderate because it changes quote-related state shape and moves totalNetworkFee for batch sells to a new selector/endpoint.

Overview
Adds BatchSell gasless trade/fee fetching via BridgeController:updateBatchSellTrades, calling the bridge API POST /obtainGaslessBatch and storing results in new state fields batchSellTrades and batchSellTradesLoadingStatus (with abort-on-new-fetch/reset and stale-data clearing on new quote requests).

Introduces selectBatchSellTrades to surface batch submittability and a computed totalNetworkFee (with currency conversions); breaking: removes totalNetworkFee from selectBatchSellQuotes.

Extends types/validators to model and validate the new response (BatchSellTradesResponse, fee schema, tx type, gas limit fields) and updates tests/snapshots accordingly; also removes some unnecessary Hex type assertions in bridge-status-controller and transaction-pay-controller.

^{Reviewed by Cursor Bugbot for commit 28e4c4c. 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 28e4c4c. Configure here.}

[cursor]

Missing optional chaining on fee causes runtime crash

Medium Severity

The selectBatchSellFees input selectors access state.batchSellTrades?.fee.amount, state.batchSellTrades?.fee.asset, and state.batchSellTrades?.fee.asset?.assetId without optional chaining after fee. The BatchSellTradesResponseSchema defines fee as optional(...), so when batchSellTrades is non-null but fee is undefined, these expressions throw a TypeError because .amount / .asset is accessed on undefined. The combiner's truthiness check doesn't help since the crash occurs in the input selectors before the combiner runs.

 

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