chore(deps): update yarn to v4

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
yarn	3.6.4 -> 4.0.0

---

Release Notes

yarnpkg/berry (yarn)

v4.0.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

[oliver-sanders]

This is pretty bleeding edge (released yesterday).

I would be tempted to hold off for a while and let others flush out issues whilst we're swamped with other things.

Changes: https://github.com/yarnpkg/berry/blob/%40yarnpkg/types/4.0.0/CHANGELOG.md

Note, Node 16 support has been dropped.

[MetRonnie]

Note, Node 16 support has been dropped.

Should be fine now because I think it was vue-cli / webpack 4 that was causing a problem before?

Also note: Node 16 already hit EOL in September - https://nodejs.org/en/blog/announcements/nodejs16-eol

[MetRonnie]

Would prefer to leave it like this, not restricting it to an env var because that's fiddly (and setting it in bashrc does not affect VSCode tasks which is how I usually run the tests 😞)

[wxtim]

I've had a good play. The only issue I found was with using Node 16, which is EOL as Oliver observed.

[MetRonnie]

@oliver-sanders Can we get this merged now? It's very fiddly to get E2E tests running on node 18+ without the vite config changes