feat: trigger qrsigning modal using approval controller

[OGPoyraz]

Development & PR Process

1. Follow MetaMask Mobile Coding Standards
2. Add release-xx label to identify the PR slated for a upcoming release (will be used in release discussion)
3. Add needs-dev-review label when work is completed
4. Add needs-qa label when dev review is completed
5. Add QA Passed label when QA has signed off

Description

The main goal of this PR is to trigger the qrsigning modal using the approval controller aligning the approach across the existing modals.

Screenshots/Recordings

1_Pair_unpair_keystone_MetaMask.mp4

2-create-token-keystone-metamask_qLMEcbFz.mp4

3_Transfer_tokens_keystone_MetaMask.mp4

4_Transfer_token_without_gas_keystone_MetaMask.mp4

5_Sign_personal_typed_keystone_MetaMask.mp4

6_Forget_this_device_keystone_MetaMask.mp4

Second round of tests:

keystone_test_1.mp4

keystone_test_2.mp4

keystone_test_3.mp4

Issue
resolves: https://github.com/MetaMask/mobile-planning/issues/783

Checklist

• There is a related GitHub issue
• Tests are included if applicable
• Any added code is fully documented

[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.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

0.0% Coverage
0.0% Duplication