fix: Fix the mobile crash due to ledger bluetooth relative exception

[dawnseeker8]

Description

This PR will fix the mobile crash issue when user disable the blind signing and reject the transaction in ledger devices.
This PR create a global exception handler to handle the bluetooth relative exception throw directly from native code, which can't be handled by our javascript code, (useLedgerBluetooth.ts has code handle those exception but shomehow, the exception still bubble up to ExceptionHandler in react native core which cause the red screen and app crash).

The global exception will specially handle the Ledger relative exception and stop exception bubble to react native core to stop app crash.

Related issues

Fixes: #11166
#11216

Manual testing steps

1. Have Ledger with Eth app 1.11.2 installed and have eth app settings on Ledger set to blind signing: disabled
2. Connect to test dapp on MM mobile browser
3. Scroll down to ERC1155 section and tap "deploy"
4. Note "Confirm transaction on your Ledger" shown on mobile client
5. Note error "Unexpected error occurred. An unexpected error occurred. Please try again"
6. Note MM closes on android and presents crash error on iOS

Screenshots/Recordings

Before

https://api.zenhub.com/attachedFiles/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBenN6Qnc9PSIsImV4cCI6bnVsbCwicHVyIjoiYmxvYl9pZCJ9fQ==--8d54ab43db845febde47fa78240c0aff20dbbff9/RPReplay_Final1728461873.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: 959d553
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/53490e11-c14b-438b-8666-50751297264f

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 passed on Bitrise! ✅✅✅

Commit hash: e897d88
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/56b59a3b-9b74-496f-af33-d59f08ae3f86

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

[Daniel-Cross]

Looks good!

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 4cb6176
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/72e705f5-f8af-4db5-ae5e-8357a4630189

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
92.3% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[vivek-consensys]

Tested on Bitrise build Android and iOS, working as expected