Add Node.js 24 to test strategy

[desrosj]

What?

This adds version 24 of Node.js to the testing strategies for workflows that test multiple versions of Node.js.

Why?

• Node.js 22 is the Active LTS version.
• Node.js 24 is the Current version and slated to become Active LTS later this year (October). This will push 22.x to Maintenance LTS.

Testing against newer versions than the one currently pinned in the WordPress Core/Gutenberg repositories helps spot potential issues ahead of time making upgrading easier when the time comes.

See related: #70844.

How?

The GitHub Actions testing strategies have been updated for workflows that currently test multiple versions of Node.js

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: desrosj <desrosj@git.wordpress.org>
Co-authored-by: aduth <aduth@git.wordpress.org>
Co-authored-by: sirreal <jonsurrell@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[aduth]

Makes sense to me assuming they already pass as-is 👍

[sirreal]

Good to get ahead of this, thanks!

[aduth]

The v24 LTS is now available. What are the next steps for making this the "default" version?

Following your earlier comment and specifically around having a "compelling argument", one relatively significant feature I'm hoping to start leveraging is native TypeScript support. For example, a lot of the new build tooling that @youknowriad has been championing through #72032 would benefit from this (example).

[jsnajdr]

Another compelling feature that is only in 24 and late 22 versions is the findPackageJSON function in the node:module package. It comes very handy in esbuild plugins for the WordPress build and we've been able to simplify out setup a lot when we discovered it.

[aduth]

Created an issue for tracking LTS update in #72973