chore: update node v22

[JamesLefrere]

Picks commits from #3456

• Updates engine and node types to v22, dropping support for older versions
• Resolves issue with outdated unicorn-magic dependency by overriding it with a fixed version

[changeset-bot]

⚠️ No Changeset found

Latest commit: f8967a2

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

[holic]

one question I have is whether the packages built under node 22 will still be usable in node 18 + 20

[JamesLefrere]

one question I have is whether the packages built under node 22 will still be usable in node 18 + 20

I have just tested this with the vanilla example with node 18, and it seems fine. Likewise, we only have the engines requirement on the root workspace, so all good there.