chore(deps): Bump `@metamask/approval-controller` from `^7.0.1` to `^7.0.3`

[MajorLift]

Description

### Changed

- Bump `@metamask/approval-controller` from `^7.0.1` to `^7.0.3` ([#11116](https://github.com/MetaMask/metamask-mobile/pull/11116))

Related issues

• Closes https://github.com/MetaMask/metamask-mobile/issues/11178

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.

[github-actions[bot]]

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.

[socket-security[bot]]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@metamask/[email protected]	None	+1	462 kB	danfinlay, gudahtt, kumavis, ...8 more

🚮 Removed packages: npm/@metamask/[email protected]

View full report↗︎

[github-actions[bot]]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: d50c0c9ef0bf5215afcdbbb19cf711f8a0588bcd Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/5f12c3a8-154c-4903-af4e-72ba403bc0c4

[!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[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarCloud

[github-actions[bot]]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: f84da3d36e20de16464341c16f9f943141143cad Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/cc235dda-a99d-4e95-bfd7-78a140e89d88

[!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[bot]]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 20d14cac6a84bfd833c6edb69834c90b727e3d30 Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/032f1882-9296-4f5a-8c88-29dc6afaee52

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

[cryptodev-2s]

closed as completed in https://github.com/MetaMask/metamask-mobile/pull/11911