javascript: add node v20 to default known versions

[kevinobruno]

Add nodejs v20 to default known versions as its the current LTS https://endoflife.date/nodejs.

I naively tried to bump the default_version to v20.11.1, but a lot of tests fails for reasons I'm still not sure.

Adding the v20 to default_known_versions at least reduces the pants.toml file when anyone wants to use the v20 as only the version option of the nodejs subsystem will need to be specified.

I plan to explore more about the upgrade from node v16 to v20 and putting a PR to change the default_version to v20 soon.

Related to #19131

[kaos]

Thanks for looking into this!

I think we want to upgrade default_known_versions at the same time as default_version. If tests starts failing, it doesn't feel like we want to say we support v20 yet.. so adding that version to default_known_versions kind of gives the wrong impression then.

[huonw]

Heya @tobni, the test failures here looks like something you might have insight into. What do you think?

[tobni]

Corepack and nodejs are distributed together. The failures are almost certainly tied to the bundled version of corepack being a later version, and either that in and of itself being a source of failure (corepack is not version 1 yet), or the newer version of corepack bumping default versions of package managers which in turn tend to not follow semver particularily well w.r.t CLI-surface. https://nodejs.org/docs/latest-v20.x/api/corepack.html

I would advice incrementing to v18 first just to see and review errors from there first.