nodejs/npm ports: segregate each, so that multiple versions can coexist side-by-side

[mascguy (Christopher Nielsen)]

Since the various NodeJS and NPM ports conflict with each other, that makes it difficult to manage dependencies for dependent components. It also precludes installing multiple versions for use/testing.

[mascguy (Christopher Nielsen)]

There is at least one open issue related to this, and perhaps there are others:

influxdb @2.0.7: buildbot builds failing, due to dependencies on both nodejs15 and nodejs16 - issue:63034

[mascguy (Christopher Nielsen)]

I'm willing to help with this, if you folks support it?

[mascguy (Christopher Nielsen)]

Given the recurring issues caused by not bring able to install various Node/NPM versions side-by-side - as well as the factvthat this limitation effectively prevents users and Devs from being able to use multiple versions at once - I'm going to prioritize this work.

We've supported side-by-side installation of much more complex stacks like Python, for a long time. And it's time we do the same for Node.

[mascguy (Christopher Nielsen)]

I'm hoping to start tackling this - starting with the oldest Node/NPM versions we provide - over the next few weeks.

It'll be an iterative process for sure, as we'll likely want to refactor shared logic to a new portgroup. But given the benefits of side-by-side installations, this will be given a reasonably high priority.

[cooljeanius (Eric Gallager)]

I think this might be causing #68726