Installer: friendlier NodeJS version

[ppawlowski]

This is a follow-up to this comment.

The suggestion is to add the possibility to provide a major NodeJS version during install/upgrade processes instead of asking to specify it in a full semver format.

@Steve-Mcl @joepavitt @knolleary @hardillb @cstns Before implementing, I would like to gather opinions on this.

[ppawlowski]

As I already mentioned, in the linked PR, I am not a fan of such approach. I prefer reproductive and predictive environments over benefits that come with pining to a major version. With strictly defined NodeJS version we give our customers a valid, verified environment, where the device agent is tested and confirmed to work properly.

[Steve-Mcl]

From a useability PoV, supporting "20" as well as "20.x.y" means users can select the major version without having to hunt down a very specific version. For example, I know I need Node 20, and I am happy with the latest, I would type "20"

This is how (for example)

• (kinda) how the official node-red installer script handles it (ref)
• how fnm handles it (fnm use 20, fnm install 22 etc) (ref)
• how nvm handles it (nvm use 20, nvm install 22 etc) (ref)
• how n (n install 22), volta (volta install node@22), brew (brew install node@22), choco (choco install nodejs-lts --version="22"), etc, install node via major number also.