[Doc] Track and report compatibility with upstream 'golden' implementation

[bbros-dev]

Track and report Cucumber-Rust compatibility with upstream 'golden' implementation.

• Cucumber Compatibility Kit
• Golden master

In order to provide this documentation the support code in the upstream Golden master needs to be ported to Rust.... essentially what Cucumber-Rust is - the Golden-Master is the reference implementation.

Related to Gherkin-Rust issues:

• Happy path specifications and data
• Unhappy path specifications and data

[bbros-dev]

From this comment, progress awaits upstream PR /cucumber/common/pull/1372
cucumber/common#1372).

running the CCK suite or producing reports. That's an exercise left to the cucumber implementation - run the features from the
CCK with support code equivalent to the example JavaScript ones, and compare the messages that come out with what the
CCK defines (with some normalisation to deal with ids, timestamps etc)

Also:

there are varying approaches between the implementations in terms of how the CCK features and messages are brought in:

• JavaScript: we publish @cucumber/compatibility-kit to npm and then import that in cucumber-js
• Java the features and messages are just copied to the cucumber-jvm repo
• Ruby, last I checked, was linking to the monorepo at a certain tag as a build step.

The current Cucmber-Rust approach is a combination of the JavaScript and Java:

• The CKK messages and fatures are copied in to Gherkin-Rust (Java)
• Gherkin-Rust is a separate crate (JavaScript)

IMO this approach is fine.

If we want a CCK report tool we'll have to roll our own.
This issue tracks the existence (or not of a CCK summary/report). Tracking how we get/update that summary in a separate issue.