Bump Version Charts workflow to Node 22

[flin-8]

Description

Third break from the same dependabot commit (5478edf), following #735 and #736.

That commit bumped @changesets/cli 2.29.8 -> 3.0.1, which requires node: ^22.11 || ^24 || >=26, but the workflow still pinned Node 20. The v3 CLI calls module.enableCompileCache() on module load, which does not exist before Node 22, so changeset version crashed immediately:

TypeError: enableCompileCache is not a function
  at @changesets/cli@3.0.1/bin.js:6:3     Node.js v20.20.2

Bumps the pin to Node 22 - the lowest supported LTS in that range. (failing run)

Verified by running the same @changesets/cli@3.0.1 binary under Node 22, which loads cleanly. cross-env@10.1.0 (the other package in that bump) only needs node: >=20, so changesets is the sole constraint.

Pre-requisites

• I have read How we use GitHub Issues for help deciding when and where it's appropriate to make an issue.
• I have added a changeset with an appropriate customer facing description.
  • CI-only change, nothing customer facing ships from it.
• I have considered appropriate testing for my change.
• This PR affects all release versions and will need to be forward merged.
  • See the documentation if unsure of the process.

[changeset-bot]

⚠️ No Changeset found

Latest commit: d648466

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