✨ S3UTILS-230 implement CRR multi-site V2 replication format

[DarkIsDude]

Summary

• Add V2 replication format support to `ReplicationStatusUpdater`, implementing the CRR to Multiple Sites design
• V2 configs (rules with a `Filter` element) route through a new `_markObjectPendingV2` path that writes per-backend `destination`/`role` and removes legacy top-level `storageClass`/`storageType`/`destination`
• V1 configs (no `Filter` on any rule) retain existing behavior unchanged
• Arsenal static methods (`resolveBackends`, `resolveSourceRole`, `resolveDestinationRole`) are reused instead of maintaining parallel implementations; arsenal dependency pinned to `improvement/ARSN-571/crr-multi`

Changes

`CRR/ReplicationStatusUpdater.js`

• `_isV1Format()` — V2 detection aligned with arsenal: a rule is V2 if it carries a `Filter` element
• `_getMatchingRules()` — prefix-matches object key against enabled rules, deduplicates by site (highest priority wins); feeds the adapter for `resolveBackends`
• `_computeTopLevelStatus()` — aggregates backend statuses: FAILED > PROCESSING > COMPLETED
• `_removeV1Fields()` — strips legacy top-level `storageClass`/`storageType`/`destination` when migrating to V2
• `_markObjectPendingV2()` — V2 metadata writer: adapts AWS SDK rule shape to arsenal's `ReplicationConfigurationMetadata`, calls `ReplicationConfiguration.resolveBackends` for prefix matching / priority dedup / per-backend destination+role stamping, then calls `resolveSourceRole` for the top-level role

`package.json` — arsenal pinned to `improvement/ARSN-571/crr-multi` for the new static methods

`tests/utils/crr.js` — V2 bucket replication config fixture

`tests/unit/CRR/ReplicationStatusUpdater.js` — 7 new V2 test cases (single match, dual-rule prefix overlap, no-match skip, SITE_NAME filter, all-up-to-date skip, PROCESSING aggregate status, forceUsingConfiguration)

Test plan

• All 456 unit tests pass (`yarn test:unit`)
• Lint clean (`yarn lint`)
• V2 metadata written with per-backend `destination`/`role` and no legacy top-level fields
• V1 configs produce identical output to before this change

Issue: S3UTILS-230

⚠️ The procedure at this page seems not up to date : https://scality.atlassian.net/wiki/spaces/TS/pages/2312536220/Ingestion+Replication+XDM#Step-one---Clear-the-replication-queue. The ENDPOINT should now be http://.... with the port :80. Should we ping CS or update the page directly ?

[codecov]

Codecov Report

❌ Patch coverage is 91.08911% with 9 lines in your changes missing coverage. Please review.
✅ Project coverage is 45.31%. Comparing base (eb9592d) to head (6ad3454).
⚠️ Report is 30 commits behind head on development/1.

Files with missing lines	Patch %	Lines
CRR/ReplicationStatusUpdater.js	91.08%	5 Missing and 4 partials ⚠️

Additional details and impacted files

@@                Coverage Diff                @@
##           development/1     #396      +/-   ##
=================================================
+ Coverage          44.90%   45.31%   +0.41%     
=================================================
  Files                 88       88              
  Lines               6456     6516      +60     
  Branches            1352     1369      +17     
=================================================
+ Hits                2899     2953      +54     
- Misses              3511     3513       +2     
- Partials              46       50       +4     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[bert-e]

Waiting for approval

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

• the author

• 2 peers

[maeldonn]

Can be simplified a lot by using arsenal logic

[bert-e]

Waiting for approval

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

• the author

• 2 peers

The following reviewers are expecting changes from the author, or must review again:

• @maeldonn

[maeldonn]

LGTM

[bert-e]

Waiting for approval

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

• the author

• 2 peers

[bert-e]

Waiting for approval

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

• the author

• 2 peers

The following reviewers are expecting changes from the author, or must review again:

• @maeldonn

[bert-e]

Waiting for approval

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

• the author

• 2 peers

[delthas]

Sorry for the delay :) Good work

[DarkIsDude]

/approve

[bert-e]

In the queue

The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.

The changeset will be merged in:

• ✔️ development/1

The following branches will NOT be impacted:

• development/1.13
• development/1.14
• development/1.15
• development/1.16
• development/1.17
• development/1.18
• development/1.4
• development/1.7

This pull request does not target the following hotfix branch(es) so they
will be left untouched:

• hotfix/1.14.0

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of the admin team will
contact you to help resolve the matter.

IMPORTANT

Please do not attempt to modify this pull request.

• Any commit you add on the source branch will trigger a new cycle after the
  current queue is merged.
• Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of the admin team now.

The following options are set: approve

[bert-e]

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

• ✔️ development/1

The following branches have NOT changed:

• development/1.13
• development/1.14
• development/1.15
• development/1.16
• development/1.17
• development/1.18
• development/1.4
• development/1.7

Please check the status of the associated issue S3UTILS-230.

Goodbye darkisdude.