S3UTILS-238: regression test for crrExistingObjects with non-ASCII keys

[tcarmet]

Intent: why does this change exist?

S3C-11235 / RD-1751 reported that crrExistingObjects fails with SignatureDoesNotMatch (HTTP 403) for any object whose key contains non-ASCII characters such as Polish diacritics, blocking the customer from replicating ~131k existing objects. The underlying bug was fixed in @scality/cloudserverclient 1.0.8, which s3utils picked up in S3UTILS-232, but no automated test exercises the path. This change adds the regression test so any future encoding regression in the dependency stack is caught in CI.

References: S3UTILS-238 · S3C-11235 · RD-1751 · CLDSRVCLT-13 · S3UTILS-232

[bert-e]

Hello tcarmet,

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.

[bert-e]

Incorrect fix version

The Fix Version/s in issue S3UTILS-238 contains:

• None

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

• 1.17.10

• 1.18.0

Please check the Fix Version/s of S3UTILS-238, or the target
branch of this pull request.

[claude]

LGTM

Review by Claude Code

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 45.02%. Comparing base (949dd51) to head (85b77e9).

Additional details and impacted files

@@                 Coverage Diff                  @@
##           development/1.17     #391      +/-   ##
====================================================
+ Coverage             44.90%   45.02%   +0.12%     
====================================================
  Files                    88       88              
  Lines                  6456     6456              
  Branches               1352     1352              
====================================================
+ Hits                   2899     2907       +8     
+ Misses                 3511     3503       -8     
  Partials                 46       46              

☔ View full report in Codecov by Sentry.
📢 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.

[claude]

LGTM

Review by Claude Code

[bert-e]

Incorrect fix version

The Fix Version/s in issue S3UTILS-238 contains:

• None

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

• 1.17.12

• 1.18.0

Please check the Fix Version/s of S3UTILS-238, or the target
branch of this pull request.

[claude]

LGTM

Review by Claude Code

[bert-e]

Incorrect fix version

The Fix Version/s in issue S3UTILS-238 contains:

• 1.17.2

• 1.18.0

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

• 1.17.12

• 1.18.0

Please check the Fix Version/s of S3UTILS-238, or the target
branch of this pull request.

[BourgoisMickael]

maybe we should also test all the utf8 unicode planes, with the 3 byte range and 4 bytes range as well. I think most of them are acceptable in s3 object key