Propose a higher minimum Node.js version for all the packages (CI related) about discussions

[UlisesGascon]

I am +1 to Dropping Support for 0.x for technical reasons 👍

Also, I am okay with supporting Dropping Support for all pre-4.x versions if we reach a good agreement.

(cc: @expressjs/express-tc )

[wesleytodd]

I think this aligns with the general idea for the main express package as well. But to be clear, this requires a major version bump for ALL of these packages. We cannot drop CI for more than a short period of time for one off reasons without major revving. We need to major a lot of them anyway, so I don't think this is a blocker.

Additionally, I tried to start this convo here #210 so not sure if we want to consolidate the discussion there and close this? Then we can circle back in the individual repos with the plan?

[ljharb]

Note that that doesn't preclude testing of any node version; I use ljharb/actions/node/install with nvm to test down to node 0.8 on 500+ projects. It just means you can't use an action that runs in node < 20 anymore, but you can still install (even with setup-node) an older version.

[inigomarquinez]

After fixing the CI of several packages in the organization, I also agree with @carpasse as he perfectly explains the problems of having to support those legacy versions.

[carpasse]

Not sure when they will enforce the change but there is a blog post from GitHub advising to migrate to node 20 on Github actions.
https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/

We've are already seen the warnings on the ci pipelines of the repos