Chore: Update all dev-dependencies

[peterkogo]

In the process of getting rid of the false-alarm security advisories on the repository, I took the time to simply update all the dev dependencies in the mono repo, and check if any major releases broke something - they did not.

[changeset-bot]

⚠️ No Changeset found

Latest commit: a64a554

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[peterkogo]

2 new typescript errors popped up.

• nodes.values().next().value.selected: object might be undefined. Fixed by: nodes.values().next().value?.selected
• For some reason PropsWIthoutRef got more strict when forwarding refs. To be fair, our type was indeed not 100% correct but props > propWithoutRef

Anyway, both seem pretty minor but I am not sure if this warrants a minor/patch because the type was changed slightly.

[moklick]

We still support React 17. This change would drop support for React17 types. Is the PropsWithoutRef change related or does it with with 17 types, too?

[peterkogo]

That might be the culprit. I did not realize that React 17 support is managed over those dependencies.

[peterkogo]

Learnings:

• We can't update past Rollup ^4.22.4 because we will get Typescript outDir to Rollup file mismatch error. With our current setup it's probably not fixable. [@rollup/plugin-typescript] tsconfig declarationDir is ignored when using single file output rollup/plugins#1230
• We can't update to ESlint 9 because setting ESLINT_USE_FLAT_CONFIG=false does not work and there are flat configs for certain libraries missing (like turbo)
• Newest typescript version pose compatibility problems (at least we now have 1 typescript version across the project)
• sometimes you need to delete all node_modules and run 'pnpm prune store' because it just does not do what it should...
• Using meta or backspace keys in playwright on Webkit does not work
• e2e is equally the most reliable and most unreliable type of testing