[Mobile snaps] Update snaps packages to version 2.0.2

[owencraston]

Description

Update snaps controller to version 2.0.2.

This also involved updating some of the peer dependancies such as @metamask/slip44, @metamask/snaps-utils", @metamask/rpc-methods.

Updated the snaps permissions titles to include the newer permissions. The list of permissions can be found here.

This changed how snap are installed now...

Before:

• installing a snap would be would trigger a wallet_installSnap approval. From this point we would parse the approval request data to show the requested permissions. We would then handle the install state internally.

Now:

• Installing a a snap triggers a wallet_requestPermissions approval type. For this we show the InstallSnapConnectionRequest. Approving this triggers a second approval request of type wallet_installSnap. This is where we show the requested permissions inside the InstallSnapPermissionsRequest. Once approved we show a success/error screen

Since the install logic relies so heavily on the the useApprovalRequest response, I moved all of the install logic from app/components/UI/... into app/components/Approvals/InstallSnapApproval

Related issues

Progresses: https://github.com/MetaMask/accounts-planning/issues/116
Fixes: https://github.com/MetaMask/accounts-planning/issues/115
Fixes: https://github.com/MetaMask/accounts-planning/issues/114

Manual testing steps

1. build branch
2. run yarn setup
3. navigate to browser tab
4. go to http://metamask.github.io/snaps/test-snaps/1.1.0
5. install BIP-32 snap
6. go through approval flow
7. the snap should be installed
8. navigate to settings/snaps
9. the snap should be available in settings
10. you should be able to preview all of the snaps permissions in the snap settings

Screenshots/Recordings

Screen.Recording.2023-11-06.at.11.39.25.PM.mov

Pre-merge author checklist

• I’ve followed MetaMask Coding Standards.
• I've clearly explained what problem this PR is solving and how it is solved.
• I've linked related issues
• I've included manual testing steps
• I've included screenshots/recordings if applicable
• 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).
• I’ve properly set the pull request status:
  • In case it's not yet "ready for review", I've set it to "draft".
  • In case it's "ready for review", I've changed it from "draft" to "non-draft".

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.

[socket-security]

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

Packages	Version	New capabilities	Transitives	Size	Publisher
@metamask/rpc-methods	0.26.2...2.0.0	None	+7/-19	2.29 MB	metamaskbot
@metamask/snaps-utils	0.26.2...2.0.1	filesystem, shell	+6/-10	1.83 MB	metamaskbot
@metamask/snaps-controllers	0.26.2...2.0.2	eval, shell	+10/-28	8.53 MB	metamaskbot
@metamask/post-message-stream	6.0.0...7.0.0	None	+0/-4	75.9 kB	gudahtt
@metamask/slip44	3.0.0...3.1.0	None	+0/-0	128 kB	metamaskbot
@metamask/permission-controller	4.0.1...4.1.2	None	+1/-5	524 kB	metamaskbot

🚮 Removed packages: [email protected]

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: @metamask/[email protected], @metamask/[email protected]

Next steps

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore [email protected] bar@* or ignore all packages with @SocketSecurity ignore-all

[owencraston]

@SocketSecurity ignore @metamask/[email protected]

[owencraston]

@SocketSecurity ignore @metamask/[email protected]

[Jonathansoufer]

LGTM. Good job and well structure code.