refactor: use @metamask/eth-qr-keyring

[mikesposito]

Description

This PR uses the @metamask/eth-qr-keyring package to handle QR code keyring functionality, replacing the previous implementation from @keystonehq/metamask-airgapped-keyring.

Along with this change, these controllers are being updated:

• keyring-controller from ^22.1.1 to ^23.1.0
• preferences-controller from ^18.4.0 to ^19.0.0
• signature-controller from ^32.0.0 to ^33.0.0

And this patch is being deleted:

• patches/@metamask+keyring-controller+22.1.1.patch - no longer needed due to the update to keyring-controller@^23.1.0

Changelog

CHANGELOG entry: null

Related issues

Fixes:

Manual testing steps

1. Go to this page...

Screenshots/Recordings

Before

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.

[sonarqubecloud]

Quality Gate failed

Failed conditions
62.9% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud

[salimtb]

assets changes lgtm