[chore] move dev env to Node.js 18

[igorDykhta]

• Node 14 and Node 16 are no longer official supported Node.js versions.

• Node 18 is now the oldest LTS release.

• Also loaders.gl has now finally updated to Node 18 which should remove one of the obstacles to upgrading Node in kepler, and conversely, kepler being on Node 18 should facilitate loaders.gl 4.0 integration.

• It looks like we need NODE_OPTIONS=--openssl-legacy-provider in a lot of extra places in addition to what was revealed by CI. Either add them or upgrade webpack to 5.x. >> Added NODE_OPTIONS in several places, ignoring a ton of rarely used places for now as almost all scripts need extra NODE_OPTIONS set.

• test website build

[ilijapuaca]

Nice work! Just out of curiosity - do we know of any substantial issues that'd stop us from upgrading to v20/21?

[ibgreen]

Nice work! Just out of curiosity - do we know of any substantial issues that'd stop us from upgrading to v20/21?

The gap from 18->20 should be much smaller than 14->18 but we don't have much test mileage on v20 yet in the open source. To avoid this dragging out I recommend landing this for now and then make a second pass towards 20 once we have worked through the big OSS upgrade cycle (all the frameworks are going through major releases).

[ilijapuaca]

The gap from 18->20 should be much smaller than 14->18 but we don't have much test mileage on v20 yet in the open source. To avoid this dragging out I recommend landing this for now and then make a second pass towards 20 once we have worked through the big OSS upgrade cycle (all the frameworks are going through major releases).

Of course, not suggesting we do additional work here, was just curious if we already spotted some potential issues with that upgrade. As you noted, there's nothing that stood out to me based on the release notes I went through though