Enhance namespace and multiple accounts support for WalletConnect

[cawfree]

It is possible for a user to connect multiple networks to the Verida account for a single dApp; however, our current UI isn't structured this way. We need to update the UX to allow users to select wallets for all protocols demanded by a particular dApp, else they should not be allowed to continue (a partial network selection is not valid).

Context: #935

[aurelticot]

With WalletConnect v2, DApps can enumerate the chains they are supporting, either as optional or required for the connection.

When connecting, the Verida Wallet receives a proposal detailing this information.
As an example, for Uniswap, the proposal looks like this when selecting Polygon Mumbai in their network selector:

{
  "optionalNamespaces": {
    "eip155": {
      "chains": ["eip155:1", "eip155:5", "eip155:11155111", "eip155:137", "eip155:80001", "eip155:42220", "eip155:44787", "eip155:56", "eip155:43114", "eip155:42161", "eip155:421613", "eip155:10", "eip155:420"],
    }
  },
  "requiredNamespaces": {
    "eip155": {
      "chains": ["eip155:80001"],
    }
  }
}

The User/Wallet is required to connect with an account/address on eip155:80001 and optionally can have additional connections with the other chains listed in optionalNamespaces, assuming there are corresponding account/address.
From a UX and security standpoint, the user should explicitly select the multiple addresses and the UI must be adapted for such cases.

As of 0.3.51 our UI doesn't allow multi-selection of addresses. This ticket aims to enable it.

There are cases where DApps could request several required chains for the connection. (at least, it's technically possible to receive such proposals).

{
  "requiredNamespaces": {
    "eip155": {
      "chains": ["eip155:5", "eip155:80001"],
    }
  }
}

Or

{
  "requiredNamespaces": {
    "eip155": {
      "chains": ["eip155:80001"],
    },
    "near": {
      "chains": ["near:testnet"],
    }
  }
}

As our UI doesn't allow multi selection, we are unable to successfully satisfy such connection request. This ticket also aims to address this.

[aurelticot]

Look at WalletConnect's Namespace Builder

https://docs.walletconnect.com/web3wallet/namespaces