chore: upgrade glob

[davidjgoss]

🤔 What's changed?

Upgrade glob to the latest version.

This includes some breaking changes from glob that have an effect on us:

• Results are no longer returned sorted - so we now do a .sort() ourselves on the array
• Backslashes are no longer considered valid in Windows paths and are interpreted as an escape character - there is a backwards compatibility option for this which we're using - I'd rather just bring users along but it will be quite an involved change and not something we need to do immediately
• Requires Node.js 18 or above - this means we should land remove support for Node.js 14 and 16 #2325 before this, although no tests have failed on 14 or 16 interestingly

Nothing breaking for our users, though.

⚡️ What's your motivation?

Fixes #2329 as the vulnerable dependency is no longer present (at least not in production code - you can see via npm ls inflight that some test packages still depend on it, but we can handle that in due course). Also just gets us current.

🏷️ What kind of change is this?

• 🏦 Refactoring/debt/DX (improvement to code design, tooling, documentation etc. without changing behaviour)
• 🐛 Bug fix (non-breaking change which fixes a defect)

📋 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.

[coveralls]

coverage: 97.931% (-0.5%) from 98.458% when pulling 28421d1 on fix/glob-upgrade into 89ec3b6 on main.