fix(11895): remove duplicate networks in incoming transactions settings

[vinnyhoward]

Description

We now list mainnet networks in the RPC urls so the previous logic rendering mainnet is no longer need. Here is the relevant PR that has those changes

Related issues

Related Issue: #11895

Manual testing steps

1. Go to this settings page
2. Click on "Security & Privacy"
3. Scroll down and toggle "Show incoming transactions" and confirm that it works
4. Confirm that the duplicate mainnet networks are gone

Screenshots/Recordings

Before	After

Before

NA

After

NA

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 started on Bitrise...🔄🔄🔄

Commit hash: 69cae3b
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/446ee62e-a4c2-4a38-a2c3-0961becdf962

Note

• This comment will auto-update when build completes
• 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 failed on Bitrise! ❌❌❌

Commit hash: 4af32bf
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/210b109c-b252-4b05-abe8-e59101ca2229

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: 6b5b819
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/db92871f-8d5c-4dae-9078-eb24702615bf

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

See analysis details on SonarCloud

[chrisleewilcox]

The app security indicates that 'Mainnet' is not the right name. Expected that the default network name matches suggested name and is aligned with security checks. We can get PM input if needed.