Update actions/setup-node action to v6

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
actions/setup-node	action	major	v5.0.0 -> v6.0.0

---

Release Notes

actions/setup-node (actions/setup-node)

v6.0.0

Compare Source

What's Changed

Breaking Changes

• Limit automatic caching to npm, update workflows and documentation by @​priyagupta108 in #​1374

Dependency Upgrades

• Upgrade ts-jest from 29.1.2 to 29.4.1 and document breaking changes in v5 by @​dependabot[bot] in #​1336
• Upgrade prettier from 2.8.8 to 3.6.2 by @​dependabot[bot] in #​1334
• Upgrade actions/publish-action from 0.3.0 to 0.4.0 by @​dependabot[bot] in #​1362

Full Changelog: actions/setup-node@v5...v6.0.0

---

Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

Upgrades the GitHub Actions setup-node action to v6.0.0 across both build and code-quality workflows, ensuring the CI pipeline uses the latest Node setup improvements.

Walkthrough

• Chore: Bumped actions/setup-node from v5.0.0 to v6.0.0 in build.yaml and code-quality.yaml, aligning CI with updated Node runner features and performance enhancements.

_{Model: o4-mini | Prompt Tokens: 764 | Completion Tokens: 681}

[github-actions]

We have prepared friendly suggestions for your code powered by AI. Some insights rely on predictions and may not always be precise, so feel free to pick what suits you best. You are in charge and make the final call, while AI serves as a supportive guide.
_{Model: o4-mini | Prompt Tokens: 1279 | Completion Tokens: 2486}

[github-actions]

Consider using a semantic version tag instead of a full commit SHA for actions/setup-node. This improves readability and makes upgrades easier. For example:

- uses: actions/setup-node@v6
  with:
    node-version-file: source-folder/.tool-versions
    cache: npm

[github-actions]

Rather than running npm prune --omit=dev after install, you can use npm ci --omit=dev for a clean, faster install of only production dependencies:

- run: npm ci --omit=dev

[github-actions]

The checkout and setup-node actions are pinned to commit SHAs. It’s more common to use tagged versions for clarity and easier upgrades. For example:

- uses: actions/checkout@v3
- uses: actions/setup-node@v6
  with:
    node-version-file: .tool-versions
    cache: npm

[github-actions]

You have duplicate checkout and setup-node steps. To DRY up this workflow, you could extract common steps into a reusable workflow or use YAML anchors. For example:

# Define anchors at the top
defaults: &checkout-and-setup
  steps:
    - uses: actions/checkout@v3
    - uses: actions/setup-node@v6
      with:
        node-version-file: .tool-versions
        cache: npm

# Reuse anchors in jobs
jobs:
  pr-lint:
    runs-on: ubuntu-latest
    <<: *checkout-and-setup
    steps:
      - run: npm ci
      - run: npm run lint

  code-scan:
    runs-on: ubuntu-latest
    <<: *checkout-and-setup
    steps:
      - run: npm ci
      - run: npm run code-scan