Update supported Node.js versions

[davidjgoss]

🤔 What's changed?

Update the tested Node.js versions to match the current and LTS versions, and other Cucumber packages.

🏷️ What kind of change is this?

• 🏦 Refactoring/debt/DX (improvement to code design, tooling, etc. without changing behaviour)
• 💥 Breaking change (incompatible changes to the API)

📋 Checklist:

• I agree to respect and uphold the Cucumber Community Code of Conduct
• I've changed the behaviour of the code
  • I have added/updated tests to cover my changes.
• My change requires a change to the documentation.
  • I have updated the documentation accordingly.
• Users should know about my change
  • I have added an entry to the "Unreleased" section of the CHANGELOG, linking to this pull request.

---

This text was originally generated from a template, then edited by hand. You can modify the template here.

[mpkorstanje]

This doesn't break anything I think?

[davidjgoss]

It’s more like drawing a line because anyone using this on say Node.js 16 might be okay today but it will break at some unknown future point when we use a new syntax or standard library function.

[luke-hill]

Don't really care how changelogs are written. For ruby updates I tend to just write updated minimum ruby to x. However I don't see a physical restriction anywhere (I don't know if this concept exists in js world).