fix: fix duplicated network select

[salimtb]

Description

his PR introduces a fix for handling multiple networks with different RPC URLs in the NetworkSelector component, along with comprehensive unit tests to ensure the component's functionality. The tests verify that only one network can be selected at a time, even when the networks have the same chain ID but different RPC URLs.

Related issues

Fixes: #11509

Manual testing steps

1. add tow different polygon network with two different rpc
2. switch between them

Screenshots/Recordings

Before

before.mov

After

after-2.mov

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 failed on Bitrise! ❌❌❌

Commit hash: 1eb05d1
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/157b0ac1-0128-4461-b6ae-8d50bc68e4ac

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]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 1ec9679
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/cc9eed9c-4b12-498e-87f3-92de627c5a5b

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

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarCloud