JS-371 - Deprecate Node.js 18

[ericmorand-sonarsource]

JS-371

[yassin-kammoun-sonarsource]

Hey @ericmorand-sonarsource, as mentioned during the standup, deprecating the support of a Node.js version requires also a bit of work on the Java side. In particular, we need to update the following:

SonarJS/sonar-plugin/bridge/src/main/java/org/sonar/plugins/javascript/bridge/NodeDeprecationWarning.java

Lines 40 to 44 in ac71cb1

	static final Version MIN_SUPPORTED_NODE_VERSION = Version.create(18, 17, 0);
	private static final int MIN_RECOMMENDED_NODE_VERSION = 18;
	private static final List<String> RECOMMENDED_NODE_VERSIONS = List.of("^18.18.0", "^20.9.0", "^22.9.0");
	private final AnalysisWarningsWrapper analysisWarnings;

Maybe we should document the process of deprecating a Node.js version to avoid tribal knowledge. Not sure where to write this down...

[yassin-kammoun-sonarsource]

Since we are only deprecating, not dropping support, maybe we should keep this as it was before.

[ericmorand-sonarsource]

This change establishes that the project needs Node 22 to be operated: you can't run the unit tests without at least Node 22.

[yassin-kammoun-sonarsource]

Let's double-check with the rest of the squad whether we still want to test SonarJS against Node.js 18 on CI.

[ericmorand-sonarsource]

@yassin-kammoun-sonarsource , issues should be fixed:

• NodeDeprecationWarning was updated
• The formatting issues on documentation were fixed
• I restored the Docker manifest to Node 18

[yassin-kammoun-sonarsource]

I left two minor suggestions about spelling, otherwise looks good to me.

[sonarqube-next]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube