Update Conformance / Use u2d versions

### 🤔 What's the problem you're trying to solve?

@ursfassler - We're now trying to get the cpp version actively supported. The next step would be to fix any wire integrations to use as close to the latest version/s as possible.

Ideally this would see us be able to release a 1.0 version of the cpp framework with late(r) versions of cpp support (Get rid of lots of legacy code / support). And then go down the traditional semver path

### ✨ What's your proposed solution?

Update to use a cucumber wire 7.x version and a cucumber-ruby 9.x version

### ⛏ Have you considered any alternatives or workarounds?

N/A

### 📚 Any additional context?

Cucumber-Wire between v2 and v5 was predominantly not changed much, it was mainly focussed on de-coupling from the cucumber-ruby implementation. As such these versions for the wire plugin can largely be perceived to be identical / having very little difference/s

Since then the main changes are just ruby / stylistic tweaks. Again not much to worry about.

The bigger concern is cucumber-ruby. This **has** changed a lot. There are some bug fixes going in recently which show some of these oddities (Such as the envelopes not looking as expected). Also some of the acceptance tests with the integrations were a bit flaky. cc/ @canmor

*This text was originally generated from a [template](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates), then edited by hand. [You can modify the template here.](https://github.com/cucumber/.github/edit/main/.github/ISSUE_TEMPLATE/feature_request.md)*