Build/Test Tools: Install the npm version required by package.json in GitHub Actions

[manzoorwanijk]

Adds a setup-npm action, mirroring WordPress/gutenberg#82775 and WordPress/gutenberg#82823, so CI installs the npm required by devEngines.packageManager even when Node.js bundles an older one. It also adds the same devEngines field as Gutenberg to package.json.

It will allow us to use the latest version of npm in CI without the EBADDEVENGINES error.

• setup-npm owns the npm cache, because actions/setup-node resolves it with the bundled npm, which fails with EBADDEVENGINES once a newer npm is required.
• Release branches run these reusable workflows from trunk against their own checkout, which lacks the action. A hashFiles gate skips it there.
• Release branches lose the npm download cache. They run rarely, and setup-node's exact key rarely hit anyway.
• Callers' paths filters now include .github/actions/setup-npm/**.

cc @desrosj: unrelated, but 6.9's test-build-processes.yml omits gutenberg-branch, so it builds Gutenberg trunk on Node.js 20 and every Gutenberg job fails with EBADENGINE. Passing gutenberg-branch: 'wp/6.9', as 6.5 to 6.8 do, we should fix it.

Trac ticket: https://core.trac.wordpress.org/ticket/66099

Use of AI Tools

AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Opus 5
Used for: Implementation and this description, reviewed by me.

🤖 Generated with Claude Code

---

This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

[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.

Core Committers: Use this line as a base for the props when committing in SVN:

Props manzoorwanijk, mciampini, adrianmoldovanwp.

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

[manzoorwanijk]

I can't request a review, so CCing you all

@desrosj @lancewillett @aduth @ciampo @jsnajdr @tyxla

[github-actions]

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

• All changes will be lost when closing a tab with a Playground instance.
• All changes will be lost when refreshing the page.
• A fresh instance is created each time the link below is clicked.
• Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
  it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

[ciampo]

LGTM 🚀

Makes sense, as per instructions.

Not sure if we should wait for more approvals, especially for folks who continute to this repo more frequently.

[manzoorwanijk]

I would appreciate it if this could be expedited; it will help prepare the repo for npm v12, which we are tracking in WordPress/gutenberg#82328

[adimoldovan]

Two findings, both inline. The first breaks a manual run of the default-themes workflow against a release branch. The second makes the theme jobs copy the core npm cache under their own keys.