WalletConnect labs testing

https://lab.web3modal.com/

**AC:**

- [ ] Wallet handles namespaces that have extra or unsupported chains, methods, events via giving feedback to the user or still approving them to handle requests for supported cases or showing user feedback latter on when performing requests for unsupported ones.
- [ ] Wallet cleans up duplicate pairings, subscriptions for same dapp (same metadata) either during disconnect or new connection. If these are left behind, initialisation of sign / web3wallet sdk can take a very long time resulting in poor ux. Use most recent pairing, session.
- [ ] Wallet handles disconnecting session correctly from both wallet and dapp side (also if this event occurs in the background i.e. user's wallet is closed and they disconnect from dapp side. Wallet should cleanup and delete such session when it boots up by listening to appropriate events).
- [x] After connection is established, there is a test "sign message" action in the laboratory, ensure that works to confirm your requests and responses are set up correctly.
- [ ] Wallet sends correct response when user rejects connection. Not doing this resulting in web3modal not knowing when to refresh qr code / connection string for further connection attempts.
- [ ] Ensure your sdk's are up to date, ideally using our new Web3Wallet sdk

### Android
| | Connect wallet | Reject connection | Switch chain | Sign message | Read Avax Contract | Disconnect |
|---------|----------------|-------------------|--------------|--------------|--------------------|------------|
| v1 | ✅ | ✅ | | ✅ | | ✅ |
| v1 extended | ✅ | ✅ | | ✅ | | ✅ |
| v2 | ✅ | ✅ | | ✅ | | ✅ |
| v2 extended | ✅ | ✅ | | ✅ | | ✅ |
| v2 standalone | ✅ | ✅ | | ✅ | | ✅ |
| v2 custom | ✅ | ✅ | | ✅ | | ✅ |

**Issues:**

- [ ] Switch chain error
- [ ] Switch chain declined