fix: remove thrown Error for logging in Sentry on unrecognized network switch

[frankvonhoven]

Description

Don't throw and Error on unrecognized network, just report it to Sentry

Related issues

Fixes: #11731

Manual testing steps

In in-app browser:

1. Go to https://bridge.coredao.org/coreBTC
2. Click on "Add coreBTC to your wallet"
3. MM should log in Sentry "Unrecognized chain ID "0x45c". Try adding the chain using wallet_addEthereumChain first."

Screenshots/Recordings

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.

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

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

See analysis details on SonarQube Cloud

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: e8416a3
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/a89fbc71-2b7e-4172-a6f4-97280f8357e7

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