chore: prepare new release and dogfood

[weboko]

Description

This task is to prepare new release of js-waku packages and dogfood it in accordance with our checklist.

The list

• npm audit returns no vulnerabilities. Vulnerable packages must be updated.
• Review open bugs and ensure no blocking / critical bugs present. If present, fix the bug and proceed with the release.
• Personally verify version works in dogfooding app for active Filter / LightPush usage for 30 - 60 min.
• Verify Store works for querying latest messages. (https://github.com/waku-org/examples.waku.org/blob/master/examples/store-js/index.html)
• Verify version works against the fleets. If no or flakiness present, root cause and communicate with the team. (use https://github.com/waku-org/js-waku/actions/workflows/fleet-checker.yml)
  • Without discovery: Dial nodes from sandbox and test fleets without using discovery. Each node should be available for dial. If any fail, it should be shared with infra and/or nwaku team
  • With discovery: run against active fleets, see how well it works, any problems with DNS quarries, WSS connection being established
• Interop tests are green, otherwise must be investigated and root caused. If nwaku has breaking changed - must be communicated with nwaku team and identified if release should proceed.
• Github checks are green.
• In case newer nwaku version is present - upgrade it in CI pipelines.
  • Look at latest release version of nwaku: https://github.com/waku-org/nwaku/releases
  • In js-waku, search for wakuorg/nwaku: across the repository to see which version is set.
• Once al of the above is complete: merge the chore: release master PR
  • If the PR is out of date with master or broken, re-run the release stage of the CI against master and it should automatically update the PR
• Make a post in announcements channel first Monday after release.
  • Copy announcement message template from https://discord.com/channels/1110799176264056863/1111568123007606855/1353765109746499624
  • Get changelog from chore: release master PR and use it to write or generate the highlights section of the announcement message
  • Reach out to other team members for any highlights
  • Send finished announcement message to Aaron or someone with publishing rights in Discord announcements channel

[weboko]

Resolved with #2390