Tune parameters to reduce intermittent failures in S3 TM pauseAndResume integ test

[alextwoods]

Tune parameters to reduce intermittent failures in S3TransferManagerDownloadPauseResumeIntegrationTest.pauseAndResume_ObjectNotChanged_shouldResumeDownload integration test.

Motivation and Context

Depending on the timing of waitUntilFirstByteBufferDelivered, the entire file may have been downloaded causing the assertThat(bytesTransferred).isLessThan(sourceFile.length()) to fail.

Modifications

This PR changes three paramters:

1. Set maxConcurrency to 1 for the CRT client.
2. Increase the file size from 24 mb to 50.
3. Decrease the waiter time from 100ms to 10ms.

Testing

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.
• 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 failed

Failed conditions
19.6% Coverage on New Code (required ≥ 80%)
27.2% Duplication on New Code (required ≤ 3%)
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

[alextwoods]

This was merged as part of #6343

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