Use Node 20, and add it to CI

[p2edwards]

Description

Update Node version to 20.17.0 for release builds, and run the frontend tests in Node 20 and 22 in CI.

Related issues

Part of #4703

Notes for devs

• Current recommended version of Node for dev is now 20.17.0.
  • The easiest way to follow these Node version bumps is with a tool like fnm or nvm.
• If you're updating npm packages (package-lock.json) yourself, please do so using Node 20.17.0 (or, in the future, the version is specified in the Dockerfile)
• We'll consider Node 20 the minimum supported version
  • Any 20 or 22 should work too, but you may get some console warnings
  • Node 16.15.0 will continue to work for a few weeks, but we'll soon upgrade npm packages that don't support Node 16.
• This mainly affects frontend developers (anyone running npm commands manually during their regular dev process, on their host machine not in the kpi container)
  • If you're running these commands inside the Docker container, and your Docker image is up to date, it will come with the OK version of Node.

Details for reviewer

Patches mocha-chrome to allow it to successfully run on Node >16 (see commit message)

Updates the recommended version of Node to v20.17.0 (the active LTS version, newest point release as of 2024-08-23)

• in the Dockerfile, used by kobo-install and the production builds
• in .node-version and .nvmrc, supporting popular tooling such as nvm and fnm, which developers may use to conveniently switch to the recommended Node version for a given project on their dev machine
• in the helper script whch shows up for developers running a different version of Node during npm install.

Runs this version v20.17.0 in the CI npm tests, as well as any available newer Node 20 or Node 22.

• To avoid invalid cache reuse when new versions become available, we use the actual resolved version as part of the cache key, rather than the generic "20" or "22" specifier.

Bumps various github action versions (actions/checkout, setup-node, setup-python), mainly to avoid deprecation warnings in CI output. Major changelogs look good to me.

Process notes

Like #4354 and #4554, test Node 20 upgrade.

troubleshooting steps

• npm run watch still works locally

the mocha-chrome problem

• Fix the broken mocha test runner in CI

Like before, the mocha test runner was in node > 16.

Run npx mocha-chrome test/tests.html --chrome-launcher.connectionPollInterval=5000
  npx mocha-chrome test/tests.html --chrome-launcher.connectionPollInterval=5000
  shell: /usr/bin/bash -e {0}
  
Promise Rejection:  Error: connect ECONNREFUSED ::1:32897
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1606:16) {
  errno: -111,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '::1',
  port: 32897
}
Error: The action 'Run Tests, with mocha-chrome' has timed out after 1 minutes.

Node 17 introduced some changes to DNS.lookup, which was the root cause of this timeout. See commit message for the fix.

follow-up

• Add newer versions of Node to the test matrix, too
• Figure out if we want to pin a precise version of Node per release, or go with 20.
  (The 16.15.0 -> 16.15.1 breakage is probably not likely to happen again, but we like stability.)
  Conclusion: Pin it