Add dependency to specifically open Metamask extension

With the increasing number of web3 extensions, services like ours (CoinRequest invoicing), have troubles with opening the correct extension. Two or more extensions installed prohibit you from choosing which one you would like to open, and in many cases make the web3 integration useless.

What would be the perfect solution is an additional dependency. There are a view wallets:
Fortmatic
Squarelink
Portis
Torus

that use this and can therefore be supported perfectly due to the ability to distinguish between them.

Example: https://coinrequest.io/request/uNdnkVCD0GrFxn8

Examples dependencies:

https://codesandbox.io/s/1r02oon46q (Portis)
https://www.npmjs.com/package/@portis/web3 (Portis dependency)
https://docs.fortmatic.com/web3-integration/web3-provider (Fortmatic)
https://www.npmjs.com/package/fortmatic (Fortmatic)

Please add this to the extension. Cheers.

No repository files, tests, or entry points are named. Start by reviewing the CoinRequest example and the linked Portis and Fortmatic dependency references, then locate the extension's web3 integration and dependency management areas. Done should mean a concrete, agreed scope for supporting a specifically selected wallet without ambiguity about the integration behavior.

Written by the indexing model from the issue text.