[bug] Bad UX when attempting to connect through MetaMask on supported networks

[majinbot]

Link to minimal reproducible example

n/a

Summary

I am silently rejected from connecting with MetaMask when attempting to connect on an unsupported network, while I am informed properly of the issue by Phantom and other wallets. Could it be the way the AppKit interfaces with MM under the hood thats suppressing visual warnings from MM?

Btw, when I try to connect through MetaMask I get the following notice in the extension
"We noticed that the current website tried to use the removed window.web3 API. If the site appears to be broken, please click here for more information."

and this warning in the browser console:
"inpage.js:1 You are accessing the MetaMask window.web3.currentProvider shim. This property is deprecated; use window.ethereum instead. For details, see: https://docs.metamask.io/guide/provider-migration.html#replacing-window-web3"

p.s. see my other issue (#2885) for error related to disconnect() func missing from AppKit class

List of related npm package versions

"dependencies": {
	"@coinbase/wallet-sdk": "^4.0.4",
	"@reown/appkit": "^1.0.2",
	"@reown/appkit-adapter-ethers": "^1.0.2",
	"ethers": "^6.13.2"
}

[kovart]

Same issue with the latest version of appkit (v1.2.0):

    "@reown/appkit": "^1.2.0",
    "@reown/appkit-adapter-ethers": "^1.2.0",