Prepare v0.9.0 release

[martin4861]

Summary

Prepare CHANGELOG.md for the next release, similar to #315.
Once merged and tagged, I will add cucumber-cpp@0.9.0 to the Bazel Central Registry.

Checklist:

• It is my own work, its copyright is implicitly assigned to the project and no substantial part of it has been copied from other sources (including Stack Overflow). In rare occasions this is acceptable, like in CMake modules where the original copyright information should be kept.
• I'm using the same code standards as the existing code (indentation, spacing, variable naming, ...).
• I've added tests for my code.
• I have verified whether my change requires changes to the documentation
• My change either requires no documentation change or I've updated the documentation accordingly.
• My branch has been rebased to main, keeping only relevant commits.

[mpkorstanje]

Once merged and tagged, I will add cucumber-cpp@0.9.0 to the Bazel Central Registry.

Why? Did you see #313?

[martin4861]

Once merged and tagged, I will add cucumber-cpp@0.9.0 to the Bazel Central Registry.

Why? Did you see #313?

Yes, I’ve been following that thread. There are still Bazel users actively relying on cucumber-cpp. We have already added v0.8.0 to the BCR, and releasing v0.9.0 would really help us upgrade to newer Clang versions.

[mpkorstanje]

Cheers. Appreciated. I'll take a look next week if Urs doesn't beat me to it.

[ursfassler]

Cheers. Appreciated. I'll take a look next week if Urs doesn't beat me to it.

Thanks for taking action @mpkorstanje.
And thanks to @martin4861 for fixing the compile error.
🙏