Doc update

[luke-hill]

🤔 What's changed?

Add testing notes RE versions in readme

⚡️ What's your motivation?

Get more clarity on what is tested

🏷️ 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)
• ⚡ New feature (non-breaking change which adds new behaviour)
• 💥 Breaking change (incompatible changes to the API)

♻️ Anything particular you want feedback on?

📋 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 is perishable information. It will go out of date when the Github Action is changed.

Consider removing the versions altogether and a second that describes how Gherkin is tested, refering to the CI files for specific versions.

[luke-hill]

Fair point. But can you help with the 2 misunderstood ones? C/Obj C? Those appear wrong / untested

[mpkorstanje]

C is tested by

https://github.com/cucumber/gherkin/blob/main/.github/workflows/test-c.yml

Objective-C is untested.

Maybe put that in the readme for objective-c.