[Ruby]: Update conformance

[luke-hill]

🤔 What's changed?

Like one or two of the repos so far (And some more to come), the conformance of the ruby side of things has been let slide for 2+ years.

This PR is the first of 3 major releases planned for tag-expressions, whereby we'll progressively bump aggressively through the legacy ruby versions (Whilst simultaneously updating dev dependencies and according cucumber-ruby testing)

⚡️ What's your motivation?

Get things up to date, with as little friction as possible

🏷️ What kind of change is this?

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

♻️ Anything particular you want feedback on?

Timings. When is this good to hit? This tends to be a repo with little to no changes coming, so mirroring up with other breaking change releases would be good.

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

[luke-hill]

@ehuelsmann tagged you for a review purely w.r.t. timings. I know you've landed a few things in recently.

If you have any medium sized things landing it would be good to land these simultaneously and cut a major revision. Happy to be guided by yourself on this. I'll be making a series of PR's here to try progressively update the deps here as we're like 7-8 years behind schedule.

[luke-hill]

Confirmed with Erik offline this is good to merge. As/when we cut the next version it'll be v6