chore: upgrade dependencies

[pvditto]

• Upgrades dependencies to latest compatible versions,
• removes pinning of react and react-dom dev-dependencies (were pinned to v18.0.0),
• updates @dittolive/ditto usage following update to latest version,
• adds karma.conf.js to .eslintignore as the project is using a Typescript linter,
• configures karma-typescript to handle ES2020 syntax used by cbor library (fixes Errors running tests using NPM #48),
• updates targeted browsers to match https://docs.ditto.live/compatibility/js-web,
• and applies all the updated linter / code style rules to the existing code.

Example project

• Upgrades dependencies,
• fixes test code,
• and adds a TextEncoder polyfill required for JSDom to support @dittolive/ditto.

CI

• Upgrades Github Actions versions and Node.js version used.

To be squash-merged.

[jreyes33]

Thanks for tackling this! LGTM, except for a small detail about how we generate changelogs.

[jreyes33]

Sorry for the lack of docs in this regard, but for the last few releases, we've been using conventional commits and standard-version to generate this changelog. I tried running it again (npx standard-version) to see what would happen with this manually added entry and it resulted in this:

### [0.11.1](https://github.com/getditto/react-ditto/compare/v0.11.0...v0.11.1) (2024-04-18)


### Bug Fixes

* remove implicit dependency on `lodash` ([9b56f93](https://github.com/getditto/react-ditto/commit/9b56f9331de4e5718478717d0c9527dca2764d15))

## [0.11.0](https://github.com/getditto/react-ditto/compare/v0.11.0-alpha.0...v0.11.0) (2023-03-22)

### Unreleased

## Changed

- browser support now matches the `@dittolive/ditto` package. see [Ditto's
  documentation](https://docs.ditto.live/compatibility/js-web)
  ([#56](https://github.com/getditto/react-ditto/pull/56))

Since this PR mainly focuses on upgrading dependencies, I wouldn't want to rewrite the whole PR's commit message when merging it just to see a new entry in the changelog. Is there a chance we could separate/reword this change to use a properly formatted commit message? Let me know if you have other ideas.

[pvditto]

Sure, I just saw the changelog and wanted to add to it. I will remove that change and update the PR title to use the standard-version syntax.

[pvditto]

Hmm, adding the markdown link to the documentation in the PR title sure looks wonky. I can squash-merge the PR with a commit message

chore: match supported browsers with the `@dittolive/ditto` package. see [Ditto's documentation](https://docs.ditto.live/compatibility/js-web) for details.

does that work? It will hide the actual (internal) changes of this PR but at least it doesn't break the changelog tool.

[jreyes33]

Yeah, I think that works. I'd just like to point out that only commits marked with feat and fix will make it to the changelog, so if you want to have that message show there you should pick one of those; if not, chore seems fine to me too.

[jreyes33]

LGTM!