Prepare Release Candidate-2 due to substantial changes after RC-1

[rartych]

Problem description
After Release Candidate-1 (RC-1) was completed, substantial changes are introduced (like updating artifacts to OWASP rules, subscription refactoring, pagination), and necessary modifications to support bundling in the release automation process. These changes are essential for API releases coming next.

Expected action
Instead of proceeding with a public release based on RC-1, prepare and validate Release Candidate-2 (RC-2) to ensure all recent changes are tested and verified before the public launch.

Additional context
Releasing RC-2 will minimize potential issues after release, and ensure the release automation with bundling works as intended.
Commonalities-Consumption-and-Bundling-Design

[hdamker]

Could we use the RC2 to align the versioning across the files to 0.8.0-rc.2? Currently is CAMARA_common.yaml ahead of the overall version of Commonalities which is somewhat confusing. I propose that all files are belonging together and - if versioned - will use the same version as the Commonalities release.

That would mean that there will be no public version 0.7.0 and we jump from 0.6.0 (Fall25) to 0.8.0 (Spring26), but that's a one-time effect.