fix(perps): skip unified migration for multi-sig accounts

[abretonc7s]

Explanation

Opening Perps for a HyperLiquid multi-sig account attempted a single-signer unified-account migration on every entry, producing Multi-sig required and recurring error reports.

This change detects the account signer set before that write, skips migration for multi-sig accounts, and caches the final non-unified readiness state. It also handles a conversion race by classifying the same rejection in the write fallback.

Validation

• Real HyperLiquid testnet account, same driver and signer:
  • main: reproduced Multi-sig required and Unified Account setup failed.
  • This branch: logged the multi-sig migration skip with neither failure.
  • The account was returned to its original single-sig/default state afterward.
• Provider regression target: 36 passed, 24 skipped.
• Error-classifier target: 19 passed.
• Provider suites: 13 suites passed; 569 tests passed, 36 skipped.
• Full @metamask/perps-controller suite and root build passed before the final rebase. Required GitHub checks provide the authoritative post-rebase validation.

This is a headless controller change, so visual evidence does not apply.

References

• Jira: https://consensyssoftware.atlassian.net/browse/TAT-3214
• Supersedes the closed Mobile workaround: fix(perps): [Bug]: Perps - Error when selecting imported account ApiRequestError: Multi-sig required metamask-mobile#34170

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 the package changelog
• I've introduced breaking changes in this PR and have prepared client updates

---

Note

Low Risk
Scoped to unified-account setup in HyperLiquidProvider with fail-open probing and extensive tests; no changes to order placement or auth beyond skipping an impossible migration.

Overview
Fixes recurring Multi-sig required failures when opening Perps for HyperLiquid accounts that were converted to multi-sig, where each visit retried a single-signer unified-account migration that the venue cannot accept.

The provider now calls userToMultiSigSigners immediately before a migration write would run (only on paths that need migration, so already-unified accounts are unchanged). Multi-sig accounts skip agentSetAbstraction / userSetAbstraction, record trading readiness as { attempted: true, enabled: false }, and emit account-setup analytics with not_applicable / multi_sig_account instead of treating setup as failed.

A new exported helper isHyperLiquidMultiSigRequiredError classifies HyperLiquid’s multi-sig rejection (both hyphen spellings). The migration catch path uses it as a fallback when the probe fails open on network errors or the account flips multi-sig between probe and write, so those cases are not logged as setup failures or retried endlessly.

Unified mode stays off for these users; HIP-3 collateral continues via the existing programmatic transfer fallback.

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