Add Cucumber tests for multi-destination CRR

[maeldonn]

Cover V2 multi-rule replication configs, mixed CRR + cloud destinations, overlap validation, disabled rules, and V1 plus legacy comma-StorageClass backward compatibility. Factor shared replication polling and replica-match helpers out of the existing single-destination steps so both single- and multi-destination scenarios reuse them.

Issue: ZENKO-5253

[SylvainSenechal]

For me it's pretty much ok, I left some comment that you can check, I think it's ok if the suggested changes aren't applied but there may be some refactoring possible to make it a bit easier to read

[delthas]

Can rebase on top of 2.16 (since #2378 was merged). Includes CRR changes.

[SylvainSenechal]

Can rebase on top of 2.16 (since #2378 was merged). Includes CRR changes.

rebase from my branch, which i also just rebased from 2.16

[SylvainSenechal]

Just nit on linter warning single line if and alignement of rules array

[delthas]

LGTM apart from comment

[delthas]

The check-workflows failure on this PR is unrelated to its changes: softprops/action-gh-release v3.0.2 (published 2026-07-13, pulled in automatically via the floating @v3 tag in release.yaml) changed its GitHub API call sequence, which breaks the tests/workflows/release.spec.ts mocks on every PR based on development/2.14+. Tracked in ZENKO-5317, fix in #2464.

[delthas]

Heads-up: the deterministic (not flaky — retries won't help) end2end-pra "PRA (nominal case)" and Kafka Cleaner CTST failures on this PR are a regression in backbeat >= 9.5.0-preview.2: alert threshold defaults like 10*60 render invalid Go-template annotations, prometheus-operator rejects the rule and aborts the entire Prometheus config sync, so the metrics these tests poll never get scraped. Tracked in BB-824, fix in scality/backbeat#2778 — bumping backbeat to 9.5.0-preview.7 once released will unblock it. (Full analysis: #2461 (comment thread).)

[bert-e]

Hello maeldonn,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options

name	description	privileged	authored
/after_pull_request	Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval	Bypass the pull request author's approval	⭐
/bypass_build_status	Bypass the build and test status	⭐
/bypass_commit_size	Bypass the check on the size of the changeset TBA	⭐
/bypass_incompatible_branch	Bypass the check on the source branch prefix	⭐
/bypass_jira_check	Bypass the Jira issue check	⭐
/bypass_peer_approval	Bypass the pull request peers' approval	⭐
/bypass_leader_approval	Bypass the pull request leaders' approval	⭐
/approve	Instruct Bert-E that the author has approved the pull request.		✍️
/create_pull_requests	Allow the creation of integration pull requests.
/create_integration_branches	Allow the creation of integration branches.
/no_octopus	Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity	Change review acceptance criteria from one reviewer at least to all reviewers
/wait	Instruct Bert-E not to run until further notice.

Available commands

name	description	privileged
/help	Print Bert-E's manual in the pull request.
/status	Print Bert-E's current status in the pull request TBA
/clear	Remove all comments from Bert-E from the history TBA
/retry	Re-start a fresh build TBA
/build	Re-start a fresh build TBA
/force_reset	Delete integration branches & pull requests, and restart merge process from the beginning.
/reset	Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

[maeldonn]

/approve

[bert-e]

Waiting for approval

The following approvals are needed before I can proceed with the merge:

• the author

• 2 peers

[bert-e]

I have successfully merged the changeset of this pull request
into targetted development branches:

• ✔️ development/2.16

The following branches have NOT changed:

• development/2.10
• development/2.11
• development/2.12
• development/2.13
• development/2.14
• development/2.15
• development/2.5
• development/2.6
• development/2.7
• development/2.8
• development/2.9

This pull request did not target the following hotfix branch(es) so they
were left untouched:

• hotfix/2.13.5

Please check the status of the associated issue ZENKO-5253.

Goodbye maeldonn.

The following options are set: approve