chore: prep for 2.9.0 release

[ganchoradkov]

Release Checklist

• Canary Version QA

  • I have thoroughly tested the release using a canary version: 2.9.0-canary.0
  • 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.

Description

• fix: switch chain by @ganchoradkov in fix: switch chain #2899
• fix(deps): update dependency @walletconnect/jsonrpc-ws-connection to v1.0.12 by @renovate in fix(deps): update dependency @walletconnect/jsonrpc-ws-connection to v1.0.12 #2908
• fix(deps): explicitly set jsonrpc-ws-connection to latest by @bkrem in fix(deps): explicitly set jsonrpc-ws-connection to latest #2913
• Add sideEffects: false to more packages by @0xasimetriq in Add sideEffects: false to more packages #2910
• feat: providers to accept empty required chains/namespaces by @ganchoradkov in feat: providers to accept empty required chains/namespaces #2781
• fix(utils): ensures RN-only Platform polyfill has exhaustive guard by @bkrem in fix(utils): ensures RN-only Platform polyfill has exhaustive guard #3008

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.