[rush] Add support for Node.js 18.x LTS

[octogonz]

Summary

@xuewan-seven pointed out that our repo doesn't support Node.js 18 in microsoft/rush-example#17

Node.js 18.x is now LTS as of 2022-10-25.

Node.js 14.x will reach end of line on 2023-04-30.

Details

• Upgrade CI pipelines
• Upgrade rush init template
• Update logic in NodeJsCompatibility.ts
• I replaced the confusing UPCOMING_NODE_LTS_VERSION constant with LATEST_NODE_LTS_VERSION

How it was tested

Tested locally. I also tested reportAncientIncompatibleVersion() by installing Node.js 8.9.0 and trying to build our repo. Rush crashed due to an unsupported RegExp, so I bumped the ancient version to 10.x

Fixes microsoft/rush-example#17

[dmichon-msft]

LGTM

[iclanton]

@TheLarkInn tried doing this last year (#3571) and we found that Webpack 4 isn't compatible with Node 18. We could try to patch that, though. IIRC, it's some change to crypto.

You also need to add 18 to this line: https://github.com/microsoft/rushstack/blob/main/.github/workflows/ci.yml#L15

[mikeharder]

Are you intentionally dropping support for Node 14? It's supported until 4/30/23.

[octogonz]

@mikeharder This is just for the rush init template that's used when people create new Git repositories. We could wait until the last day to adjust it, but I worried that it might take us months to remember to do that. 😆 You can of course put whatever range you like in your own rush.json.

If you think it's important for some reason let me know.

[mikeharder]

Personally, I would err on the side of allowing older Node versions beyond EOL, rather than dropping support for active Node versions. But I agree customers can change this after rush init if they want, so it's not too important.

[octogonz]

Superseded by #4278