fix(perps): tpsl builder fee readiness

[geositta]

Explanation

The first TP/SL edit after Mobile reload could fail before cancellation or placement because the builder-fee approval lookup sent the one-off maxBuilderFee request over a reconnecting WebSocket. HyperLiquid rejected it with WebSocketRequestError, which updatePositionTPSL surfaced as TPSL_UPDATE_FAILED; a later retry succeeded after reconnection.

This routes builder-fee approval reads through the existing HTTP InfoClient, which is designed for request/response operations and remains available during WebSocket churn. maxBuilderFee was not a subscription, so this does not remove live updates or change existing approval-cache semantics. Genuine approval failures still block replacement before existing protection is cancelled.

Adds regression coverage with distinct WebSocket and HTTP clients and updates the perps-controller changelog. No dependencies or other packages are changed.

Validation:

• Full @metamask/perps-controller test suite
• Builder-fee and strategy-order suites
• Monorepo build
• Changelog validation and scoped lint/format checks
• Mobile simulator: first +50/-50 TP/SL edit succeeded after reload

References

• Discovered while validating #9995

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

Low Risk
Narrow transport change for a read-only approval lookup on an existing HTTP code path; regression test covers the TP/SL cold-start scenario.

Overview
Fixes a case where the first position TP/SL update after app reload could fail with TPSL_UPDATE_FAILED because the builder-fee approval check (maxBuilderFee) went over a reconnecting HyperLiquid WebSocket and threw WebSocketRequestError.

#checkBuilderFeeApproval in HyperLiquidProvider now requests the info client with useHttp: true, so that read uses the HTTP InfoClient path that stays usable during socket churn. Approval caching and real approval/signing behavior are unchanged; only the lookup transport changes.

Adds a regression test that simulates a failing WebSocket maxBuilderFee and asserts cold-start updatePositionTPSL succeeds via HTTP, plus an Unreleased changelog entry.

^{Reviewed by Cursor Bugbot for commit 3e2cffb. Bugbot is set up for automated code reviews on this repo. Configure here.}