chore: Drop Node <18 support

[JPeer264]

closes #2985

This will ensure that in the future don't have to work around certain features which are not available in older Node versions.

[andreiborza]

Hm, don't think we can/should do this. The CLI is used by our bundler plugins which are used by our SDKs which still support node 18 🤔.

[JPeer264]

Very good point @andreiborza - Node 18 is good as well

[andreiborza]

You typod the node version in the win32-x64 json, otherwise LGTM.

Should the base branch be master tho? How are you and @szokeasaurusrex handling v3?

[szokeasaurusrex]

@andreiborza I have a PR stack for the 3.0 major. Currently the top PR is #2973.

I see two options for how we handle this: either we can have a separate PR stack for the JS API changes, which we can merge together at the end. This could make sense as we hopefully will not have too many conflicts at the merge.

The other option is we add this PR to my stack. That avoids merge conflicts in the future. In that case, I would take over managing this PR's branch once we agree it is ready, as the PR stacking process requires a rebase/force push workflow.

Which would y'all prefer?

[andreiborza]

@szokeasaurusrex I leave that up to you and @JPeer264, personally I'd add this to your stack.

[szokeasaurusrex]

Looks good!

[szokeasaurusrex]

@JPeer264, I have added some suggestions. Once you have finalized your changes, please rebase on top of the v3 branch and resolve any conflicts. Once you are all done, please let me know, and I'll take over the branch and add it to my stack.