Update 3rd party actions within composite action.

[desrosj]

What?

This updates the 3rd party actions used within the setup-node composite action. Unfortunately, it seems that Dependabot does not currently update workflows found outside of the .github/workflows directory, so these have fallen out of date.

[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: kevin940726 <kevin940726@git.wordpress.org>

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

[github-actions]

Flaky tests detected in 3c3923f.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/8883214740
📝 Reported issues:

• [Flaky Test] Redirection after template creation #60678 in /test/e2e/specs/site-editor/site-editor-url-navigation.spec.js

[kevin940726]

Thanks!

[desrosj]

After creating this PR, a new feature was announced as public beta where you can specify multiple directories for a package ecosystem. It's unclear if this would solve the problem addressed here. Some more testing is needed. Let's merge this for now and try that out separately!

[DaniGuardiola]

Heads up that the Windows version of this CI task is failing for me, not sure if due to this change though: https://github.com/WordPress/gutenberg/actions/runs/8908331640/job/24463757246?pr=61138

[DaniGuardiola]

This seems related: npm/cli#7308

[desrosj]

It looks like your PR is the first one making a change to the package.json file after this PR was merged, which means it's the first one running the npm ci step.

There are some similar (though not exact) reports in the actions/setup-node repo. I did not see anything obvious looking at the release log there. Though the most recent version (4.0.2) did add support for arm64 on Windows.

I tried rolling that back in a test PR and it worked for me: https://github.com/WordPress/gutenberg/actions/runs/8911422697. I've gone and created #61289 to apply this change.