fix: fix 11836 wrong accounts in 2 ledger devices

[dawnseeker8]

Description

This PR will fix #11835 issue, the details of this PR change include following:

1. Fix the useBluetoothDevices.ts infinitely loop to setDevices due to devices properties in outside scope of observable inside next() function (devices always is empty object)
2. Fix the scan.tsx component which always select the first devices due to above change.

Related issues

Fixes: #11835

Manual testing steps

1. Install MM
2. Recover from SRP
3. Pair Ledger Nano X to MM
4. Pair Ledger Stax to MM
5. Select Ledger Nano X and verify account list derived from device
6. Select Ledger Stax and verify account list derived from device

Expected:- 2 different account lists for each device

Screenshots/Recordings

Before

https://api.zenhub.com/attachedFiles/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBOFJUQnc9PSIsImV4cCI6bnVsbCwicHVyIjoiYmxvYl9pZCJ9fQ==--0c57025402bf0df5c50f0a5247c29ddf56cc7e60/RPReplay_Final1729159957.MP4

After

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.

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.

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 92a3852
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/7d48030c-bdba-4934-86bd-debd76b5f1f4

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 164aa26
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/ab59b73b-5ca5-4815-888a-7ea2ffd6064f

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

Tip

• Check the documentation if you have any doubts on how to understand the failure on bitrise

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 4a15c38
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/3646c8a2-046e-4141-be9d-369b2499b4e1

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

Tip

• Check the documentation if you have any doubts on how to understand the failure on bitrise

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: d56463e
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/bf19d89c-b7e4-4a4b-941c-9f3c47c857bd

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud