fix: fix infura key displayed

[salimtb]

Description

We are exposing our network API keys in the network verification details. Exposing API keys should be avoided due to their significant security risks.

To reproduce:
Go to networks view
Proceed to add any infura supported network from the popular network list. Polygon is a good example.
Notice in the network approval modal the Infura API key is exposed in the Network URL field.

Related issues

Fixes: #1574

Manual testing steps

1. Go to the add network page
2. Choose polygon and click on add
3. A modal will be displayed, scroll down to see the RPC Url
4. Infura url should not display the api key

Screenshots/Recordings

Before

After

trim.88505A2C-3CE8-4514-B44E-EC105C1864C2.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). Not required for external contributors.
• 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.

[github-actions]

E2E test started on Bitrise: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/966032bd-ffbc-4e7d-bd9e-ca97d3d98038
You can also kick off another Bitrise E2E smoke test by removing and re-applying the (Run Smoke E2E) label

[Cal-L]

Left a comment

[github-actions]

E2E test started on Bitrise: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/78ee69f9-ceb0-4d9e-aec3-3c2088655df0
You can also kick off another Bitrise E2E smoke test by removing and re-applying the (Run Smoke E2E) label

[sonarcloud]

Quality Gate passed

Issues
0 New issues

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

See analysis details on SonarCloud

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 41.43%. Comparing base (6ddffcf) to head (dc03284).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #8744      +/-   ##
==========================================
+ Coverage   41.41%   41.43%   +0.01%     
==========================================
  Files        1270     1270              
  Lines       30826    30833       +7     
  Branches     3042     3043       +1     
==========================================
+ Hits        12768    12775       +7     
  Misses      17295    17295              
  Partials      763      763              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Cal-L]

LGTM

[metamaskbot]

Missing release label release-7.17.0 on PR. Adding release label release-7.17.0 on PR and removing other release labels(release-7.18.0), as PR was cherry-picked in branch 7.17.0.