chore(main): release 2.21.0

[github-actions]

🤖 I have created a release beep boop

What's Changed

• feat: Moving from ipfs-http-client -> kubo-rpc-client by @whizzzkid in feat: Moving from ipfs-http-client -> kubo-rpc-client #1124
• fix: removed state change notifications by @whizzzkid in fix: removed state change notifications #1123
• feat: add E2E tests for chromium and firefox by @galargh in feat: add E2E tests for chromium and firefox #1121
• chore: CODEOWNER meandavejustice->whizzzkid by @SgtPooki in chore: CODEOWNER meandavejustice->whizzzkid #1135
• fix: 🐛 waiting for test to finish for longer by @whizzzkid in fix: 🐛 waiting for test to finish for longer #1136
• chore: add sourceMaps to dev-builds by @SgtPooki in chore: add sourceMaps to dev-builds #1134
• chore: update PRIVACY-POLICY.md by @SgtPooki in chore: update PRIVACY-POLICY.md #1137
• feat: add telemetry to companion by @SgtPooki in feat: add telemetry to companion #1117

New Contributors

• @galargh made their first contribution in feat: add E2E tests for chromium and firefox #1121

Full Changelog: v2.20.1...v2.21.0

---

This PR was generated with Release Please. See documentation.

[welcome]

Thank you for submitting this PR!
A maintainer will be here shortly to review it.
We are super grateful, but we are also overloaded! Help us by making sure that:

• The context for this PR is clear, with relevant discussion, decisions
  and stakeholders linked/mentioned.

• Your contribution itself is clear (code comments, self-review for the
  rest) and in its best form. Follow the code contribution
  guidelines
  if they apply.

Getting other community members to do a review would be great help too on complex PRs (you can ask in the chats/forums). If you are unsure about something, just leave us a comment.
Next steps:

• A maintainer will triage and assign priority to this PR, commenting on
  any missing things and potentially assigning a reviewer for high
  priority items.

• The PR gets reviews, discussed and approvals as needed.

• The PR is merged by maintainers when it has been approved and comments addressed.

We currently aim to provide initial feedback/triaging within seven business days. Please keep an eye on any labelling actions, as these will indicate priorities and status of your contribution.
We are very grateful for your contribution!

[whizzzkid]

@lidel I think we'll have to manually fix this first release because the semver from last release was missed and it's not computing the title again.

Also, why don't we have a version entry in the package.json?

[whizzzkid]

I think rerunning this workflow should do the trick, closing this.