feat(NODE-7007)!: remove support for node 16 and 18

[durran]

Description

Drops support for Node 16 and 18

What is changing?

• Updates Node 16 CI tasks to run on Node 20, 22, 24.
• Fixes the windows 2019 blackout issue on actions.

Is there new documentation needed for these changes?

Manual updates for supported versions.

What is the motivation for this change?

NODE-7007

Double check the following

• Ran npm run format:js && npm run format:rs script
• Self-review completed using the steps outlined here
• PR title follows the correct format: type(NODE-xxxx)[!]: description
  • Example: feat(NODE-1234)!: rewriting everything in coffeescript
• Changes are covered by tests
• New TODOs have a related JIRA ticket

[baileympearson]

Cannot comment on the following because they're out-of-diff:

• can we audit our dependabot config for any packages we can now update because we no longer support Node16 and 18?
• Can we update the readme's compat table with accurate glibc requirements (if they have changed), now that we're Node 20+?

[nbbeeken]

This happened last time we did a major, double check the ! is in the right position 😅 next to the :

[durran]

This happened last time we did a major, double check the ! is in the right position 😅 next to the :

👍

[baileympearson]

Some additional changes I cannot comment on because they're out-of-diff:

• There are more occurrences of Node16 in the build action that should be updated
• There's logic to set ubuntu_version in our yml files that can go away (UBUNTU_VERSION can probably be removed entirely as an argument to the dockerfile too)
• can we audit our dependabot config for any packages we can now update because we no longer support Node16 and 18?
• Can we update the readme's compat table with accurate glibc requirements (if they have changed), now that we're Node 20+?

[durran]

Some additional changes I cannot comment on because they're out-of-diff:

* There are more occurrences of Node16 in the build action that should be updated

* There's logic to set `ubuntu_version` in our yml files that can go away (UBUNTU_VERSION can probably be removed entirely as an argument to the dockerfile too)

* can we audit our dependabot config for any packages we can now update because we no longer support Node16 and 18?

* Can we update the readme's compat table with accurate glibc requirements (if they have changed), now that we're Node 20+?

I've updated everything except UBUNTU_VERSION, since it was actually needed for the builds to run.

[baileympearson]

Cannot comment because it isn't in the diff

1. docker.sh still defaults to Node18. Can we update that to Node20 as well?
2. I think we can update nyc now, and remove the exception from our dependabot config (nyc's next major version is Node18+, which is why we haven't upgraded)

[baileympearson]

@durran Can we also increase our ecmascript target in the eslint config to 2023 (https://node.green/#ES2023)?

[durran]

@durran Can we also increase our ecmascript target in the eslint config to 2023 (https://node.green/#ES2023)?

Done