• fix: hw account abstraction migration (fix: hw account abstraction migration cp-7.77.0 #30114)

Description

This PR prevents Perps from triggering browsing-time signing flows for
hardware wallet users while the screen is idle.

Previously, Unified Account setup only deferred the dexAbstraction
migration when user signing was not allowed. Other signing-backed
HyperLiquid abstraction modes could still attempt setup during passive
Perps initialization, which could surface repeated hardware wallet
prompts without an explicit user action.

The fix adds a shared helper for deciding when Unified Account setup
must be deferred, applies it during HyperLiquid provider initialization,
and expands hardware wallet detection to cover MetaMask's hardware
keyring types: Ledger, Trezor, OneKey, Lattice, and QR hardware wallets.
Software wallets can still complete setup during initialization so the
first trade sees unified collateral, while hardware wallets defer setup
until an explicit trading or withdrawal action.

Changelog

CHANGELOG entry: Fixed a bug that could repeatedly prompt hardware
wallet users while Perps was idle.

Related issues

Fixes:

Manual testing steps

Feature: Perps hardware wallet idle setup

  Scenario: Hardware wallet user opens Perps and leaves it idle
    Given the user has selected a Ledger, Trezor, OneKey, Lattice, or QR hardware wallet account
    And Perps is enabled and available

    When the user opens the Perps screen
    And leaves the Perps screen idle without placing an order, withdrawing, or otherwise starting a signing action
    Then the app does not repeatedly show hardware wallet signing prompts

Feature: Perps software wallet setup

  Scenario: Software wallet user opens Perps
    Given the user has selected a software wallet account that needs Unified Account setup

    When the user opens the Perps screen
    Then Perps can complete the setup flow during initialization
    And the first trade can use unified collateral without an extra setup step

Screenshots/Recordings

N/A. This is a controller behavior change with no intended UI changes.

Before

N/A

After

N/A

Pre-merge author checklist

• I've followed MetaMask Contributor
  Docs and MetaMask Mobile
  Coding
  Standards.
• I've completed the PR template to the best of my ability
• I've included tests if applicable
• I've documented my code using JSDoc format
  if applicable
• I've applied the right labels on the PR (see labeling
  guidelines).
  Not required for external contributors.

Performance checks (if applicable)

• I've tested on Android
  • Ideally on a mid-range device; emulator is acceptable
• I've tested with a power user scenario
• Use these power-user
  SRPs
  to import wallets with many accounts and tokens
• I've instrumented key operations with Sentry traces for production
  performance metrics
• See trace() for usage and
  addToken
  for an example

For performance guidelines and tooling, see the Performance
Guide.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the
  app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described
  in the ticket it closes and includes the necessary testing evidence such
  as recordings and or screenshots.