Backport of chore(deps): bump actions/setup-node from 4.0.3 to 4.0.4 into release/1.8.x

[hc-github-team-nomad-core]

Backport

This PR is auto-generated from #24032 to be assessed for backporting due to the inclusion of the label backport/1.8.x.

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@pkazmierczak
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.

merge conflict error: POST https://api.github.com/repos/hashicorp/nomad/merges: 409 Merge conflict []

The below text is copied from the body of the original PR.

---

Bumps actions/setup-node from 4.0.3 to 4.0.4.

Release notes

Sourced from actions/setup-node's releases.

v4.0.4

What's Changed

• Add workflow file for publishing releases to immutable action package by @​Jcambass in actions/setup-node#1125
• Enhance Windows ARM64 Setup and Update micromatch Dependency by @​priyagupta108 in actions/setup-node#1126

Documentation changes:

• Documentation update in the README file by @​suyashgaonkar in actions/setup-node#1106
• Correct invalid 'lts' version string reference by @​fulldecent in actions/setup-node#1124

New Contributors

• @​suyashgaonkar made their first contribution in actions/setup-node#1106
• @​priyagupta108 made their first contribution in actions/setup-node#1126
• @​Jcambass made their first contribution in actions/setup-node#1125
• @​fulldecent made their first contribution in actions/setup-node#1124

Full Changelog: actions/setup-node@v4...v4.0.4

Commits

• 0a44ba7 Correct version string (#1124)
• 97ca147 Merge pull request #1125 from actions/add-is-release-workflow
• aa363de Create publish-immutable-action.yml
• 1c7b2db Fix: windows arm64 setup (#1126)
• 26961cf Documentation update in the README file (#1106)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

---

Overview of commits

• 0788aeb

[hashicorp-cla-app]

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

---

temp seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA.
If you have already a GitHub account, please add the email address used for this commit to your account.

_{Have you signed the CLA already but the status is still pending? Recheck it.}

[hashicorp-cla-app]

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

---

temp seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA.
If you have already a GitHub account, please add the email address used for this commit to your account.

_{Have you signed the CLA already but the status is still pending? Recheck it.}

[github-actions]

Ember Test Audit comparison

	release/1.8.x	8405567	change
passes	1569	1569	0
failures	2	2	0
flaky	0	0	0
duration	000ms	000ms	-000ms