CLDSRV-909: Reject CopyObject when source exceeds 5 GiB

[tcarmet]

Align cloudserver's CopyObject with the AWS S3 contract by rejecting requests whose source object exceeds 5 GiB. AWS S3 returns HTTP 400 InvalidRequest ("The specified copy source is larger than the maximum allowable size for a copy source: 5368709120") and expects clients to use the multipart copy flow instead; cloudserver currently accepts these requests, leaving a gap with the published contract.

Targeting development/9.4 because changing a previously-accepted response is a behavior break for clients that relied on cloudserver's permissive behavior, happy to retarget development/9.3 if we prefer wider rollout.

Last commit contains a prettier fmt command and is kept separate from the actual code change for review. We should not focus on it as most of it is existing change.

[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 CLDSRV-909 contains:

• None

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

• 9.4.0

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

[claude]

LGTM

Review by Claude Code

[codecov]

❌ 1 Tests Failed:

Tests completed	Failed	Passed	Skipped
9409	1	9408	0

View the full list of 1 ❄️ flaky test(s)

"after each" hook for "should fail if trying to overwrite a delete marker"::MPU with x-scal-s3-version-id header With v4 signature "after each" hook for "should fail if trying to overwrite a delete marker"

Flake rate in main: 100.00% (Passed 0 times, Failed 41 times)

Stack Traces | 0.015s run time

We encountered an internal error. Please try again.

To view more test analytics, go to the Test Analytics Dashboard
_{📋 Got 3 mins? Take this short survey to help us improve Test Analytics.}

[claude]

LGTM

Review by Claude Code

[claude]

• config.bypassMaxPutObjectSize leaks if the bypass test fails — reset it in the after block (tests/unit/api/objectCopy.js:660)

Review by Claude Code

[claude]

• config.bypassMaxPutObjectSize cleanup in the bypass test is inside the callback — if the assertion throws, the flag leaks. Move the reset into the after() block.
  • See inline comment on tests/unit/api/objectCopy.js:790

Review by Claude Code

[claude]

• config.bypassMaxPutObjectSize is not restored in the after() block of the 'objectCopy source size limit' test suite — if the test callback doesn't run (timeout, sync throw), the flag leaks to subsequent suites.
  - Add config.bypassMaxPutObjectSize = false; to the after() block.
  
  Review by Claude Code

[claude]

LGTM

Review by Claude Code

[claude]

LGTM

Review by Claude Code

[claude]

• tests/unit/api/objectCopy.js:1908 — uses err.is.InvalidRequest instead of err.message for the error assertion; prefer assert.strictEqual(err.message, 'InvalidRequest') so failures show the actual error name
  
  Review by Claude Code

[tcarmet]

/approve

[bert-e]

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

• ✔️ development/9.4

The following branches have NOT changed:

• development/7.10
• development/7.4
• development/7.70
• development/8.8
• development/9.0
• development/9.1
• development/9.2
• development/9.3

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

• hotfix/7.10.15
• hotfix/7.70.73
• hotfix/7.4.5
• hotfix/7.10.0
• hotfix/6.4.7
• hotfix/7.10.30
• hotfix/7.10.49
• hotfix/7.4.4
• hotfix/7.6.0
• hotfix/7.70.51
• hotfix/7.4.1
• hotfix/7.10.28
• hotfix/7.9.0
• hotfix/7.4.9
• hotfix/7.4.0
• hotfix/7.4.8
• hotfix/7.7.0
• hotfix/7.70.45
• hotfix/7.4.7
• hotfix/9.0.32
• hotfix/7.70.11
• hotfix/7.10.1
• hotfix/7.2.0
• hotfix/7.8.0
• hotfix/7.70.21
• hotfix/7.10.8
• hotfix/7.10.3
• hotfix/7.4.6
• hotfix/7.4.3
• hotfix/7.10.27
• hotfix/8.8.45
• hotfix/7.10.4
• hotfix/7.4.10
• hotfix/9.2.24
• hotfix/7.10.2
• hotfix/7.4.2
• hotfix/9.0.7

Please check the status of the associated issue CLDSRV-909.

Goodbye tcarmet.

The following options are set: approve