feat: multichain popular network dapp connection confirmation bottomsheet

[EtherWizard33]

Description

It's rather simple all it does is modify the content of an existing screen.
And it does so behind a feature flag, meaning it keeps the previous UI when the flag is false, and shows the modified version if the flag is true.

Related issues

Contributes to solve issue https://github.com/MetaMask/MetaMask-planning/issues/2803

Manual testing steps

1. from a dapp tab, in the dapp, switch network to polygon
2. the bottom sheet seen below will show

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: 27661cc
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/bb95f343-0ca0-4a32-9011-421aad3e7e60

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

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: a1f417f
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/2d19cc25-4bde-45cf-8dc7-187078d09c02

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
77.1% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[mirceanis]

Looks good.
I think adding a test would help

[EtherWizard33]

Looks good. I think adding a test would help

Hi Mircea, for this feature, like for the network UI redesign me and Salim from assets worked on last month, David Walsh wants us to write e2e and unit test at the end, before removing the the feature flag, this way the code is done and stable and any unecessary e2e tests and unit tests are removed/replaced at the same time. And the added advantage is that any existing unit tests, including snapshots, ensure that the UI when feature flag is off, does not change until we are ready to move from the old code to the new.

David is OOO this week and not there to explain this reasoning more in detail, but we did this for the network ui redesign also, still behind feature flag.

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: f3e5853
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/aefcf283-1468-4e6a-9548-308e52947f60

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

[mirceanis]

looks good