Multiple Web3 provider support test

Clean install

• Verify on a clean profile(no MM, no CW enabled), visiting a web3 page only prompts to setup CW as default
• Verify setting CW as default and installing MM doesn't prompt to setup web3 provider
• Verify if None is selected, extension is lazy loaded for both CW and MM
• Verify if Crypto Wallet is selected, there is no prompt shown when visiting a web3 page and automatically connects to CW
• Verify there is no MetaMask entry in the drop down when the extension is not installed
• Verify MetaMask entry is shown in the drop down when the extension is installed
• Verify if MetaMask is selected, there is no prompt shown when visiting a web3 page and automatically connects to MM

Upgrade with an existing web3 handler

• Verify having a local account on CW on previous version and upgrading to new version retains CW as the provider
• Verify setting Crypto Wallet and installing MM in previous version and upgrading stills uses CW as the provider
• Verify disabling CW and installing MM on previous version and upgrading to new version retains MM as the provider
• Verify if CW component is downloaded on previous version and MM is not installed on previous version, upgrading to new version sets CW as the default provider
• Verify if CW component is downloaded on previous version and MM is installed on previous version, upgrading to new version sets Ask as the default option

Upgrade without web3 handler set

• Verify without without a provider (CW/MM) set in previous version and upgrading to new version sets default Ask as the option
• Verify disabling CW and not installing MM on previous version and upgrading to new version sets provider setting to None