Error: Stop throwing error in Sentry when user tries to add a chain with unrecognized rpc url

[sentry-io]

Sentry Issue: METAMASK-MOBILE-2DVH

Error: {"code":4100,"message":"Request blocked due to spam filter."}
  at ?anon_0_ (app/util/Logger/index.ts:83:32)
...
(11 additional frame(s) were not displayed)

Steps to reproduce:

• Go to https://bridge.coredao.org/coreBTC
• Click on "Add coreBTC to your wallet"
• MM will throw "Unrecognized chain ID "0x45c". Try adding the chain using wallet_addEthereumChain first."

Here we throw a Sentry error while we'd like to send and Error event in Segment instead.

[gauthierpetetin]

By the way, we don't seem to be throwing the error in Extension as I don't find any error when searching for "Unrecognized chain ID" is Sentry. We might want to take inspiration of the way it's handled in the Extension codebase.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity in the last 90 days. It will be closed in 7 days. Thank you for your contributions.

[frankvonhoven]

I think this is where
they handle that error on extension

[smilingkylan]

Also throws this error at times. Sentry seems to think it's the same issue.

Error: {"code":-32002,"message":"Request of type 'wallet_requestPermissions' already pending for origin infinifi.xyz. Please wait."}
at ?anon_0_ (app/util/Logger/index.ts:83:32)
...
(11 additional frame(s) were not displayed)

#13911

[gauthierpetetin]

Same os for unrecognised chainId, it seems we need to throw the error for the dapp without throwing it to Sentry.