Fix checksum tests

[zoewangg]

Motivation and Context

The parameterized checksum tests in MultipartClientChecksumTest has hardcoded switch statement: multipartUpload_withChecksumValueProvided_shouldUseSameAlgorithmForUploadAndAddChecksumTypeFullObject used a switch over ChecksumAlgorithm to call the corresponding setter (e.g., checksumCRC32(), checksumSHA256()). Every time a new checksum algorithm is added to the S3 model, this test would fail to compile until manually updated.

Modifications

• Replaced the hardcoded switch statement with dynamic SdkField-based value setting. The test now finds the matching field via "Checksum" + algorithm on PutObjectRequest.Builder.sdkFields() and calls field.set(), following the same pattern used in SdkPojoConversionUtils.
• Re-enabled the two parameterized test methods that were previously commented out.
• Added multipartUpload_withMd5ChecksumValueProvided_shouldPassThrough — verifies that a pre-computed MD5 checksum value is forwarded through CreateMPU, UploadPart, and CompleteMPU requests with FULL_OBJECT checksum type.
• Added multipartUpload_withMd5ChecksumAlgorithmProvided_shouldThrowException — verifies that setting checksumAlgorithm(MD5) (asking the SDK to compute MD5) throws an exception with "MD5 is not supported".

Testing

• Added unit tests
• Ran existing tests

All MultipartClientChecksumTest tests pass.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Checklist

• I have read the CONTRIBUTING document
• Local run of mvn clean install -pl :s3 succeeds for affected modules
• My code follows the code style of this project
• My change requires a change to the Javadoc documentation
• I have updated the Javadoc documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed
• I have added a changelog entry
• My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

• I confirm that this pull request can be released under the Apache 2 license

[sonarqubecloud]

Quality Gate passed

Issues
5 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

This pull request has been closed and the conversation has been locked. Comments on closed PRs are hard for our team to see. If you need more assistance, please open a new issue that references this one.