feat: 2795 disconnect all account permission multichain edit account screen

[EtherWizard33]

Description

Behind feature flag for now, adds the ability to disconnect all accounts from the edit account screen.

Related issues

Contributes to resolving: https://github.com/MetaMask/MetaMask-planning/issues/2795

Manual testing steps

1. Connect one or more account(s) to a dapp in the in app browser
2. Select the dapp, in the header click the account avatar, a bottom sheet comes up, click Disconnect, a confirmation modal will show up.
3. Click Disconnect, then a toast should show up.

Screenshots/Recordings

Before	After

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]

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 passed on Bitrise! ✅✅✅

Commit hash: b32eeb2
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/e8b6ba86-d8c9-4c21-9f82-2eb0694aaf62

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

[tommasini]

LGTM! We are solving the audit ci issue as we speak, let's merge it after

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 74fa468
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/6811fb7b-f106-4490-b2c0-9a012d376871

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

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

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

See analysis details on SonarCloud