chore: prep for 2.10.6 release

[ganchoradkov]

Release Checklist

• Canary Version QA

  • I have thoroughly tested the release using a canary version: 2.10.6-rc-0.1
  • The canary version has been verified to work as expected.
  • All major features and changes have been tested and validated.

• Web3Modal Team QA

  • The Web3Modal team has tested the release for compatibility and functionality.
  • The release is backwards compatible with Web3Modal.
  • Any reported issues or bugs have been addressed or documented.

• React Native Team QA

  • The React Native team has tested the release for compatibility and functionality (if relevant).
  • The release works correctly in React Native environments and is backwards compatible with Web3Modal React Native.
  • Any reported issues or bugs have been addressed or documented.

Related Issues and Pull Requests

• chore: prep for 2.10.5 release by @ganchoradkov in chore: prep for 2.10.5 release #3904
• chore(deps): bump @babel/traverse from 7.22.4 to 7.23.2 by @dependabot in chore(deps): bump @babel/traverse from 7.22.4 to 7.23.2 #3788
• chore(deps-dev): bump axios from 1.4.0 to 1.6.2 by @dependabot in chore(deps-dev): bump axios from 1.4.0 to 1.6.2 #3935
• chore(deps-dev): bump postcss from 8.4.21 to 8.4.31 by @dependabot in chore(deps-dev): bump postcss from 8.4.21 to 8.4.31 #3747
• chore(deps-dev): bump browserify-sign from 4.2.1 to 4.2.2 by @dependabot in chore(deps-dev): bump browserify-sign from 4.2.1 to 4.2.2 #3839
• feat: deeplink fallback by @ganchoradkov in feat: deeplink fallback #3939
• fix: pair flow by @ganchoradkov in fix: pair flow #3944
• fix: URI validation by @ganchoradkov in fix: URI validation #3960
• chore(deps): bump react-devtools-core from 4.27.8 to 4.28.5 by @dependabot in chore(deps): bump react-devtools-core from 4.27.8 to 4.28.5 #3901
• feat: expose error types by @Tuditi in feat: expose error types #3992

Definition of Done

• The release has been tested using a canary version.
• The release has been reviewed and approved by the Web3Modal team (if relevant).
• The release has been reviewed and approved by the React Native team (if relevant).
• All necessary documentation, including API changes or new features, has been updated.
• Any dependent changes have been merged and published in downstream modules.
• All tests (unit, integration, etc.) pass successfully.
• The release has been properly versioned and tagged.
• The release notes and changelog have been updated to reflect the changes made.

Please ensure that all the items on the checklist have been completed before merging the release.

[xzilja]

Left small suggestion

[xzilja]

Perhaps pin all versions to their strict options i.e. remove ^ and re-run npm install without lockfile?