Support MRAP buckets in S3 TransferManager

[alextwoods]

Support MRAP buckets in S3 TransferManager.

Motivation and Context

Fixes: #3984

S3 MRAP now supports all multi-part operations.

Modifications

• Remove check for MRAP ARN.

Testing

New unit tests.
Removed skip for MRAP buckets in existing TM regression tests (so no new tests needed to be added - existing tests will now run on an MRAP bucket). Example log lines:

2026-04-28 13:40:38 [main] INFO  software.amazon.awssdk.services.s3.regression.upload.UploadTransferManagerRegressionTesting:43 - Running putObject with config: UploadConfig(bucketType=MRAP, forcePathStyle=false, requestChecksumValidation=WHEN_SUPPORTED, bodyType=BUFFERED_SPLITTABLE_UNKNOWN_CONTENT_LENGTH, contentSize=LARGE, payloadSigning=false)

Screenshots (if appropriate)

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 install succeeds
• 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. Adding a new entry must be accomplished by running the scripts/new-change script and following the instructions. Commit the new file created by the script in .changes/next-release with your changes.

License

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

[alextwoods]

Removing this enables running all of the tests on MRAP buckets as well.

[Fred1155]

Do we need to run a one off test for CRT path?

[alextwoods]

Do we need to run a one off test for CRT path?
Yeah, I did run one-off tests for the upload TM regression tests using the CRT client instead. This path is implicitly tested already through the UploadCrtRegressionTesting and I wanted to avoid adding new, slow tests so I didn't add new tests.

[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.