feat(ci): bump node to next LTS (v22)

[HoloTheDrunk]

Description

Update the CI's node version to the next LTS version 22.

Motivation and Context

Node version 18 will soon (6 months from now) stop being supported, and some
packages require a higher version.

[jailln]

Good idea but I remember that @mgermerie started to update it to node 20 and had some issues, see #2268 . For instance commit-message-checker seems to be compatible with node 16 (however the ci works on your PR so it may be a non problem). Can you verify that the listed actions are still working as we expect them to please?

[HoloTheDrunk]

(however the ci works on your PR so it may be a non problem)

As far as I can tell the ci forces the actions to run with our specified node version and the PR ones are running properly. I'm unsure how I could test the other actions that are meant to publish the release/package/github pages without catastrophic consequences to be completely honest.

I reckon switching to other, maintained actions would be better done in other PRs, as this one is mainly meant to fix the blocking error on the lru-cache PR.

[jailln]

You can test it on your itowns fork by creating an npm account, configuring your fork to release to npm, opening this PR to your fork and merge it there. Let me know if that works. I can help if needed, I've already done it a few months ago.

[HoloTheDrunk]

This has now been tested and everything is working fine! https://github.com/HoloTheDrunk/itowns/actions/runs/11703242249
Seems like it just runs all of them by forcing node 20 and that isn't causing any issues.