Description

Re-enables the MultichainAccountSelectorList test for filtering across multiple wallets.

This test was disabled in #26377 (chore: skip failing MultichainAccountSelectorList test) as a temporary CI unblocker while the failure was investigated. Leaving it skipped removes coverage for a real user path: searching for an account when account groups are spread across more than one wallet.

The test now passes on current main with the existing deterministic FlashList mock and search wait helper, so this PR restores that coverage without changing production code.

Changelog

CHANGELOG entry: null

Related issues

Fixes: N/A

Part of INFRA-3513.

Manual testing steps

Feature: Multichain account selector search

  Scenario: user searches across multiple wallets
    Given the account selector has accounts in two wallets

    When user searches for "Account 2"
    Then only "Account 2" remains visible

Verified:

• git diff --check HEAD~1..HEAD
• yarn eslint app/component-library/components-temp/MultichainAccounts/MultichainAccountSelectorList/MultichainAccountSelectorList.test.tsx
• Targeted Jest run reports the unskipped test as passing locally; this worktree has an unrelated post-run Jest OOM also reproduced with an unrelated test file.

Screenshots/Recordings

N/A - test-only change.

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.