Update Node and NPM requirements for DSpace 11

[mwoodiupui]

Describe the bug

Current documentation requires Node v20, v22 or v24. By the time DSpace 11 ships, v22 and v24 will be EOL and v26 will be Current LTS. We should consider raising the requirement to at least v24, preferably v24 or v26. This also affects NPM: the current requirement ties it down at v10. We should investigate the work which may be required by these proposed upgrades.

Related work

#6165 discusses a warning that arises when building for Node v24.

[mwoodiupui]

https://nodejs.org/en/about/previous-releases

[alanorth]

Thanks @mwoodiupui. Another thing to consider is our Angular version. According to the Angular version compatibility page, Angular 20.3 which is used on current main works with Node versions 20, 22, and 24.

Testing with Node v24 and NPM 11, there is this security-related warning during npm install:

npm warn install-scripts 6 packages have install scripts not yet covered by allowScripts:
npm warn install-scripts   @parcel/watcher@2.5.1 (install: node scripts/build-from-source.js)
npm warn install-scripts   core-js@3.49.0 (postinstall: node -e "try{require('./postinstall')}catch(e){}")
npm warn install-scripts   cypress@15.21.1 (postinstall: node dist/index.js --exec install)
npm warn install-scripts   esbuild@0.28.1 (postinstall: node install.js)
npm warn install-scripts   lmdb@3.4.2 (install: node-gyp-build-optional-packages)
npm warn install-scripts   msgpackr-extract@3.0.4 (install: node-gyp-build-optional-packages)
npm warn install-scripts
npm warn install-scripts Run `npm install-scripts ls` to review, or `npm install-scripts approve <pkg>` to allow.

I continued to build and test without running or approving any install scripts and the build worked fine and npm run test completed with all tests passing:

$ CHROME_BIN=/usr/bin/chromium npm test
...
SUMMARY:
✔ 5930 tests completed
ℹ 2 tests skipped
TOTAL: 5930 SUCCESS
TOTAL: 5930 SUCCESS

So this is a pretty good sign nothing is obviously broken. We could even solve the problematic package-lock.json NPM compatibility issue by switching to Node 24 / NPM 11+ with DSpace 11.