Improve Handling of gherkin updates

[aepfli]

We are creating more and more gherkin updates within this repository, but we do not have a releasing process for them. Hence updates might be difficult, and it is hard to track, if i use this repo as a submodule to see, what changes are added, and that this update of the submodule might break my tests, as there are new tests.

We should think about how we can transparently communicate the gherkin updates via releases or similar mechanics.

Questions in the back of my head:

• can the gherkin tests be released separately as an own version, or do they need to be in sync with the spec version?
• can we utilize release-please to automate this process?
• can we reduce the number of approvers for the gherkin tests?

wdyt?

[aepfli]

Generally the question if we also want to run release-please within this repo - there are changes which are currently not part of a version, and we might want to consider "releasing" them under a specific version