chore(core): update `actions/setup-node` to `v4` in `ci-workflow` generator

[LayZeeDK]

Currently, the following warning is output when using GitHub Actions.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Current Behavior

• The actions/setup-node GitHub Action is installed in version 3.x which uses the deprecated Node.js 16 runtime for GitHub Actions

Expected Behavior

• The actions/setup-node GitHub Action is installed in version 4.x which uses the supported Node.js 20 runtime for GitHub Actions

Related Issue(s)

Fixes #

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

Name	Status	Preview	Updated (UTC)
nx-dev	⬜️ Ignored (Inspect)	Visit Preview	Jul 23, 2024 9:22am

[nx-cloud[bot]]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 77a9f0fb7fd34e778bdc1c9cab2a37ea624fa587. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 4 targets

• nx affected --targets=lint,test,build,e2e,e2e-ci --base=21cb71437779f390901bec3877a6876375f636b3 --head=77a9f0fb7fd34e778bdc1c9cab2a37ea624fa587 --parallel=3
• nx run-many -t check-imports check-commit check-lock-files check-codeowners documentation --parallel=1 --no-dte
• nx-cloud record -- nx format:check --base=21cb71437779f390901bec3877a6876375f636b3 --head=77a9f0fb7fd34e778bdc1c9cab2a37ea624fa587
• nx documentation --no-dte

---

Sent with 💌 from NxCloud.

[LayZeeDK]

I need a little help to update the Jest snapshots in the workspace project.

I don't have Rust on my local Windows machine and pnpm errs in the dev container.

I'll try to solve it but if someone with write permissions could update the relevant Jest snapshots, that would be great.

[github-actions[bot]]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.