Implement a wallet provider for wallet connect 2

[roxaneletourneau]

Is your feature request related to a problem and use case? Please describe.

Allow dapps to connect to wallets through wallet connect 2. Allow to send operations and sign payload.

Describe the solution you'd like

• Create a new package for wallet connect 2. The WalletConnect2 class implements the WalletProvider interface and acts as a wrapper around the wc sign client. WalletConnect2 is intended to be used in dapps in a very similar way to BeaconWallet.
• Allow to configure WalletConnect2 with an existing pairing
• Allow to configure WalletConnect2 with a new pairing/session using the QR code modal
• Allow to configure WalletConnect2 with an existing session
• wc2 allows to connect to multiple accounts; add a method setActiveAccount that the dapp needs to call to specify which account is used; the method needs to be called every time the active account is changed in the dapp
• Namespace validate; reject the session if the namespace returned by the wallet is invalid
• Permission handling; reject operation if the session doesn't have the correct permission
• Add a listener for session_delete. It informs when a session is deleted on the wallet side. If the topic of the deleted session corresponds to the topic of the session member in the WalletConnect2 class, set session to undefined.
• Add listeners for session_update, to update the session stored in the WalletConnect2 class accordingly.
• What happens if the chain/network is changed in the wallet? Can we give permission for multiple networks at once? (Yes) How to know what is the active network?
• What happens if the account is changed in the wallet? Which event listener needs to be used?
• Add unit tests
• Add a parameter named registryUrl to the requestPermissions method that allows specifying wallets displayed in the Modal.
• Provide a default list of all Tezos wallets compatible with wc2 that can be passed as the registryUrl param.