@W-14545340@ Add support for node 20

[wjhsf]

Description

This PR adds support for node 20/npm 10, mostly by just updating our engines to allow it. Note that Managed Runtime does not currently support node 20, so this does not validate deployed apps beyond "can be built with node 20 and executed with node 18".

As discovered in #1535, upgrading to node 20 mitigates one out of memory issue present in node itself. However, after a bit of testing, this did completely mitigate the issue.

Types of Changes

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Documentation update
• Breaking change (could cause existing functionality to not work as expected)
• Other changes (non-breaking changes that does not fit any of the above)

Breaking changes include:

• Removing a public function or component or prop
• Adding a required argument to a function
• Changing the data type of a function parameter or return value
• Adding a new peer dependency to package.json

Changes

• (change1)

How to Test-Drive This PR

To test functionality:

• install node 20 / npm 10
• check out code
• run every npm script in every package
• generate extensible app
• run every npm script in extensible app
• generate non-extensible app
• run every npm script in non-extensible app

To test OOM issue, start the dev server and then execute the following script from packages/template-retail-react-app. It updates a file, waits 3 seconds, then makes a request. It repeats until the app crashes or we reach 1000 iterations. Running this locally, I had the app crash after 59 iterations for node 18 and 69 iterations for node 20.

for i in $(seq 1 1000); do
  echo "// $i" >> app/constants.js
  sleep 3
  code=`curl -sSI -o /dev/null -w "%{http_code}" http://localhost:3000` || break
  echo "$i: $code"
done

Checklists

General

• Changes are covered by test cases
• CHANGELOG.md updated with a short description of changes (not required for documentation updates)

Accessibility Compliance

You must check off all items in one of the follow two lists:

• There are no changes to UI

or...

• Changes were tested with a Screen Reader (iOS VoiceOver or Android Talkback) and had no issues
• Changes comply with WCAG 2.0 guidelines levels A and AA
• Changes to common UI patterns and interactions comply with WAI-ARIA best practices

Localization

• Changes include a UI text update in the Retail React App (which requires translation)

[adamraya]

Changes to engines are missing in -lock.json files.

pwa-kit/package-lock.json

Lines 25 to 28 in 23705b4

	"engines": {
	"node": "^16.11.0 || ^18.0.0",
	"npm": "^8.0.0 || ^9.0.0"
	}

[adamraya]

Why do we define only Node 18 and Node 20 on a generated project, while we define Node 16, Node 18, and Node 20 in monorepo packages?

[wjhsf]

I didn't want to break existing projects, if we have any customers who are still using node 16 for local development. (Which would be weird, but technically possible.) For newly generated projects, though, we don't have to worry about supporting legacy versions!

[adamraya]

Sounds good. I thought that was the case, in theory dropping Node 16 would be a breaking change.

[adamraya]

LGTM!
I smoke-tested the generated template-retail-react-app project using Node 20 locally and things work as expected.
I don't see new warnings or errors when running npm i locally using Node 20.

[wjhsf]

Fixes #1618.