fix: Selecting custom ethereum mainnet on fresh install

[tommasini]

Description

On fresh install, there was an error when the user wanted to change to a custom rpc url of ethereum, because there was no other network configurations to override at that point

Related issues

Fixes:

Manual testing steps

1. Fresh install
2. Press change rpc url of ethereum before importing account
3. write the custom rpc url
4. add it successfully

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I’ve followed MetaMask 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: 9899331
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/1bc201fb-eb61-4670-ba71-4cb3d96f2d74

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
0 New issues
0 Accepted issues

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

See analysis details on SonarCloud

[legobeat]

Great catch! I guess we should also have a test for this, to prevent future regressions?