fix: Currently keystone lib will throw KeystoneError#Tx_canceled which will crash the mobile app

[dawnseeker8]

Description

This PR will fix #13259 issue.
When user reject signature in QR screen, the @keystonehq/metamask-airgapped-keyring will throw KeystoneError#Tx_canceled error. however, for some reason, Hermes engine threat that error as object and go to Crash flow.
I have fixed it by adding above uncatch error into our global ErrorHandler.ts to specially thread it.

Related issues

Fixes:

Manual testing steps

  Scenario: Swap with QR account and Reject QR modal
  
  GIVEN I have QR account selected
  WHEN I swap
  AND Reject QR modal
  THEN modal is closed (FAILED: app closes and crash alert is displayed)
  AND app is still functioning (FAILED)

Screenshots/Recordings

Before

Screen.Recording.2025-01-29.at.12.39.27.PM.mov

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 failed on Bitrise! ❌❌❌

Commit hash: 3f111a8
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/319d0e08-9dae-4048-b3a2-546701068b66

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

[sonarqubecloud]

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 SonarQube Cloud

[sethkfman]

LGTM