use previously working node version until rush issue is fixed (backport #6611) [release/4.5.x]

[mergify]

Latest nodejs security patch breaks rush integration on Windows: https://nodejs.org/en/blog/vulnerability/april-2024-security-releases-2/

This can get builds moving again until the issue is fixed. We can also hold if we think it's worth waiting for.

See:

• [rush] Latest Node LTS security patch for spawnSync breaks rush on Windows microsoft/rushstack#4636
• Fix use of spawn on windows with cmd files node-red/node-red#4652
• [rush] child_process.spawnSync on windows must set shell: true when targeting a .cmd file  microsoft/rushstack#4637

---

This is an automatic backport of pull request #6611 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of 3a8593d has failed:

On branch mergify/bp/release/4.5.x/pr-6611
Your branch is up to date with 'origin/release/4.5.x'.

You are currently cherry-picking commit 3a8593d961.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   common/config/azure-pipelines/jobs/docs-build.yaml
	modified:   common/config/rush/pnpm-config.json
	modified:   core/backend/package.json
	modified:   test-apps/display-test-app/android/imodeljs-test-app/app/build.gradle
	modified:   test-apps/display-test-app/ios/imodeljs-test-app/imodeljs-test-app.xcodeproj/project.pbxproj
	modified:   tools/internal/ios/core-test-runner/core-test-runner.xcodeproj/project.pbxproj

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   common/changes/@itwin/core-backend/mitigate-rush-nodejs-lts-builds_2024-04-12-18-10.json
	both modified:   common/config/azure-pipelines/ci.yaml
	both modified:   common/config/azure-pipelines/integration-validation.yaml
	both modified:   common/config/azure-pipelines/jobs/fast-ci.yaml
	both modified:   common/config/rush/pnpm-lock.yaml

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[aruniverse]

@mdastous-bentley can you take a look at failing map-layers-auth tests?

[mdastous-bentley]

@mdastous-bentley can you take a look at failing map-layers-auth tests?

@aruniverse Should be good now... I used fetch-mock package to solve the problem.

[hl662]

/azp run iTwin.js

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).