Update WalletConnect eth_RequestAccounts flow along with update WC deps and add new optional params

[Adamj1232]

Description

Update WalletConnect eth_RequestAccounts flow as there was an issue with creating the connect listener after the connect() method was called

Update WC deps:

"@walletconnect/ethereum-provider": "2.4.10" -> "2.5.4"

Add new optional params qrModalOptions?: Web3ModalConfig exposed with the new WC dep:

type WalletConnectOptions = {
  bridge?: string // default = 'https://bridge.walletconnect.org'
  qrcodeModalOptions?: {
    mobileLinks: string[] // set the order and list of mobile linking wallets
  }
  connectFirstChainId?: boolean // if true, connects to the first network chain provided
  /**
   * Optional function to handle WalletConnect URI when it becomes available
   */
  handleUri?: (uri: string) => Promise<unknown>
} & (
  | {
      /**
       * Defaults to version: 1 - this behavior will be deprecated after the WalletConnect v1 sunset
       */
      version?: 1
    }
  | {
      /**
       * Project ID associated with [WalletConnect account](https://cloud.walletconnect.com)
       */
      projectId: string

      /**
       * Defaults to version: 1 - this behavior will be deprecated after the WalletConnect v1 sunset
       */
      version: 2
      /**
       * List of Required Chain(s) ID for wallets to support in number format (integer or hex)
       * Defaults to [1] - Ethereum
       * The chains defined within the web3-onboard config will define the
       * optional chains for the WalletConnect module
       */
      requiredChains?: number[] | undefined
      /**
       * `undefined` by default, see https://docs.walletconnect.com/2.0/web3modal/options
       */
      qrModalOptions?: Web3ModalConfig
    }
)

Fixes #1608

Checklist

• Increment the version field in package.json of the package you have made changes in following semantic versioning and using alpha release tagging
• Check the box that allows repo maintainers to update this PR
• Test locally to make sure this feature/fix works
• Run yarn check-all to confirm there are not any associated errors
• Confirm this PR passes Circle CI checks
• Add or update relevant information in the documentation

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated
web3-onboard-docs	❌ Failed (Inspect)			Mar 31, 2023 at 9:37PM (UTC)

[leightkt]

When trying to connect an infinity wallet via walletconnect on the demo- I get the following errors in the console:

Is there another way I can test this update?

[Adamj1232]

When trying to connect an infinity wallet via walletconnect on the demo- I get the following errors in the console:

Is there another way I can test this update?

@leightkt
Not all wallets(in fact not very many) support walletconnect v2 fully. You can try Trust Wallet mobile or use the WC teams recommended testing tool: https://react-web3wallet.vercel.app/walletconnect
To do this hit the copy button on the upper right of the QR code within the WC modal and past the URI into the site above.

Judging from Infinity wallets github commit history I would be surprised if they have WC v2 support integrated

[Adamj1232]

@leightkt for a more complete list of larger wallets that do and dont support walletconnect v2 checkout - https://medium.com/walletconnect/weve-reset-the-clock-on-the-walletconnect-v1-0-shutdown-now-scheduled-for-june-28-2023-ead2d953b595

[leightkt]

Was able to successfully connect wallet from https://react-web3wallet.vercel.app/walletconnect to demo