PFM-TASK-8334 - Roll out Node 24.20.0 to github-actions repo

[senthanal]

Rolls Node 22.15.0 -> 24.20.0 and npm -> 11.19.0.

Files changed

• .github/workflows/fe-build.yml
• .github/workflows/fe-check-upmerge.yml
• .github/workflows/fe-cleanup-snapshots.yml
• .github/workflows/fe-code-quality.yml
• .github/workflows/fe-e2e.yml
• .github/workflows/fe-install-deps.yml
• .github/workflows/fe-licenses.yml
• .github/workflows/fe-pr-close.yml
• .github/workflows/fe-pr-snapshot.yml
• .github/workflows/fe-release.yml
• .github/workflows/fe-snapshot.yml
• .github/workflows/fe-tag.yml
• .nvmrc
• .tool-versions
• package.json

Deliberately not done

• No milestone is set — no matching milestone exists in either repository.
• The cplace-asc package version is not bumped; what 2.4.x starts at is a human decision.
• README.md is not touched in either repository.
• cplace-asc@2.4.x was pushed without review — confirm the new trigger exclusion.
• asc-2-asc-local.ts TOOL_VERSIONS_CONTENT still emits a nodejs line with no npm line, so generated consumer .tool-versions files differ from the two target repositories.
• cplace-asc@master's CI trigger still excludes '!2.3.x'; that line is out of scope for this roll out and stays as it is.

Needs your attention

• package-lock.json was regenerated by npm install in both repositories and committed separately. Its contents were not verified beyond the install exiting zero.
• apps/assets-compiler-e2e/package.json moved @types/node across two majors to 24.13.0 — a correction of existing drift, but a behaviour change on that branch.
• github-actions package.json moved @types/node to 24.13.0, keeping its caret range. That crosses a major for the repository that type-checks its own actions.
• On cplace-asc@2.4.x, engines.npm moves from 10.9.2 to 11.19.0, unifying it with NPM_VERSION — a correction, but a behaviour change on that branch.

ResolvesPFM-TASK-8334
´changelog´: Platform Experience: [PFM-TASK-8334] Functionality: Node 24.20.0 rollout [PR github-actions#179]

[slaven3kopic]

Do we need to adjust something in warn-foreign-registry.sh?

[senthanal]

Do we need to adjust something in warn-foreign-registry.sh?

It's version agnostic!