Fix TransferManager resume corrupting ranged downloads

[S-Saranya1]

Motivation and Context

S3TransferManager.resumeDownloadFile computes the wrong Range header when resuming a ranged download. The resume path in ResumableRequestConverter#resumedDownloadFileRequest uses bytes=bytesTransferred-contentLength (whole object size), ignoring the original range offset. This produces a silently corrupt file, wrong bytes, wrong size, no error.

Modifications

ResumableRequestConverter: extracted range computation into computeResumedRange and parseRange. When the original request had a range, the resumed range is now bytes=(originalStart+bytesTransferred)-originalEnd. Non-ranged downloads fall through to the existing behavior.

Testing

• ResumableRequestConverterRangedResumeTest: unit tests verifying correct Range header computation for ranged downloads (multiple offset scenarios) and non-ranged regression.
• ResumeRangedDownloadWireMockTest: end-to-end WireMock test validating actual file content on disk after ranged and non-ranged resume.
• CrtTransferManagerPauseAndResumeTest: added ranged resume test for the CRT transfer manager path.
• All existing tests pass.

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

Pending review of new changes.

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