(Spike) Investigate whether we can adjust the minimum compatible Node.js version to 16 or 18 for v9

[lforst]

Description

• We should check all the relevant tooling and usage numbers on whether it makes sense to require our users to use Node.js 18 or whether to bumping to 16 from 14 is a better idea.
• Once we have figured out the above it would make sense to write down a support schedule in the docs.

[lforst]

Stats from https://nodedownloads.nodeland.dev/ on Oct 2024:

• 22: 8,133,143 (5.33% of supported versions)
• 20: 68,059,075 (44.63% of supported versions)
• 18: 55,335,774 (36.28% of supported versions)
• 16: 15,615,730 (10.24% of supported versions)
• 14: 5,339,420 (3.50% of supported versions)

[lforst]

Checking internal numbers - even though the Node.js downloads show 16 has still a lot of usage - we may wanna think about dropping 16.

[lforst]

We'll drop 14 and keep 16 support

[lforst]

Due to #14570 we may need to revisit because OTEL may require 18+