CCK upgrade paths

### 🤔 What's the problem you've observed?

We're very far behind of CCK conformance

### ✨ Do you have a proposal for making it better?

Upgrade to CCK v22 in the v11 of cucumber-ruby. Then do the following upgrade paths

~22->24~
- ~Likely to involve some breaking changes in namespacing of CCK proper~
- ~Will add in a few more samples - including a test run exception~

~24->26~
- ~Should be a fairly lightweight upgrade~
- ~Changes structure of some internals (So refactoring might be needed)~

26->29
- Internal structure changes again
- Lots of new status style samples

### 📚 Any additional context?

By the time these 3 upgrade paths have been done, we may have need for another set of upgrades

No files, tests, or entry points are named. Start by locating the current CCK integration and conformance checks, then review the upgrade requirements for CCK v22 and the 22→24, 24→26, and 26→29 paths; done means cucumber-ruby reaches CCK v29 conformance with the required samples and any needed internal refactoring.

Written by the indexing model from the issue text.