Remove compatibility-kit to its own repo

[mattwynne]

🤔 What's the problem you've observed?

Break up the monorepo

TODO

• Copy commits over to https://github.com/cucumber/compatibility-kit/
• Replace path dependencies on compatibility kit with dependency on published package instead
• Remove the compatibilty-kit folder
• Move any tickets over to https://github.com/cucumber/compatibility-kit/

---

This text was originally generated from a template, then edited by hand. You can modify the template here.

[aurelien-reeves]

For the polyglot repo to be ready, we need to:

• Move features and ndjson into a samples folder (in progress: refs. Create a devkit compatibility-kit#4)
• Validate ndjson files against schemas
  • Publish json schemas with @cucumber/messages NPM package [Messages][JavaScript] Add schemas to npm package #2010
• Make ruby tests pass
• Create test-ruby.yml github workflow
• Consider validating ndjson messages against schemas in a Github workflow
• Cleanup the repo from mono-repo related stuff
• Make release workflows
• Make a release
• Rewrite README to match the actual CCK
• Add a CONTRIBUTING document

[aurelien-reeves]

"Contributing" is part of the devkit readme: https://github.com/cucumber/compatibility-kit/blob/main/devkit/README.md#contributing-to-the-compability-kit