Infra: FE: migrate to node 22

[yeikel]

What changes did you make? (Give an overview)

Node 18 reached end of life in 18 Oct 2023. The latest LTS version of Node is 22.x

See https://endoflife.date/nodejs

How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

• Unit checks
• Integration checks
• Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings (e.g. Sonar is happy)
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged

A picture of a cute animal (not mandatory but encouraged)

[Haarolean]

Sorry I'm not quite familiar with how this works, won't we get any potential issues if versions like 23.x will be used one day?

[yeikel]

You are right in your suspicions, thank you!

I updated it ba033d6 to use the ^ to only allow the current major version:

Greater than or equal to 22.12.0
Less than 23.0.0 (the next major version)

Please note that in our current configuration, we are not strictly enforcing this so it only produces a log message:

 WARN  Unsupported engine: wanted: {"node":"^22.12.0"} (current: {"node":"v23.5.0","pnpm":"9.15.3"})
Lockfile is up to date, resolution step is skipped

If the intention was to block installation, we would need to use Strict engine checks.