Add UploadIniaited, Completed, and Failed event progress trackers to MultipartUploadCommand

[GarrettBeatty]

Same as #4039 but for multi part upload command

This change creates 3 event progress trackers for MultipartUploadCommand. UploadInitiatedEvent, UploadedCompletedEvent, and UploadFailedEvent. This allows the user to subscribe to events like doing below

        private void uploadStarted(object sender, UploadInitiatedEventArgs args)
         {
             Console.WriteLine($"Upload started: {args.FilePath}");
             Console.WriteLine($"Total size: {args.TotalBytes} bytes");
             Console.WriteLine($"Bucket: {args.Request.BucketName}");
             Console.WriteLine($"Key: {args.Request.Key}");
         }


         TransferUtilityUploadRequest request = new TransferUtilityUploadRequest();
         request.UploadInitiatedEvent += uploadStarted;

These new events should only be fired 1 time during the entire lifecycle of the upload. The details of what each event should contain is in the SEP.

Some of the events (UploadCompleted) also have new TranserUtilityUploadResponse object as per the SEP requirements. This contains all of the common fields between the low level PutObectResponse and CompleteMultipartUploadResponse.

Just as an FYI will also eventually be returning TransferUtilityUploadResponse object to the user when we create the new apis UploadWithResponseAsync

TranserUtilityUploadResponse = transerutiltiy.UploadWithResponseAsync(TransferUtilityUploadRequest req) // in the future

As per the SEP requirements, I have added unit tests using the mapping.json file from the SEP, which verify that all required fields in CompleteMultipartUploadResponse are mapped to TransferUtilityUploadResponse.

Description

1. DOTNET-8276

Motivation and Context

This is being done as part of the SEP compliance.

Testing

1. Integration tests/unit tests which demonstrate the event handler behavior
2. dry run 64013b1c-44b4-43bd-b559-a92830effa41

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• My code follows the code style of this project
• My change requires a change to the documentation
• I have updated the documentation accordingly
• I have read the README document
• I have added tests to cover my changes
• All new and existing tests passed

License

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

[Copilot]

Pull Request Overview

This PR adds comprehensive multipart upload lifecycle event tracking to the S3 Transfer Utility, including initiated, completed, and failed events for both seekable and unseekable streams. It also introduces response mapping functionality to convert CompleteMultipartUploadResponse to TransferUtilityUploadResponse for consistent response handling.

Key changes:

• Added lifecycle event handling (initiated, completed, failed) for multipart uploads
• Implemented response mapping between CompleteMultipartUploadResponse and TransferUtilityUploadResponse
• Enhanced progress tracking with comprehensive test coverage for various upload scenarios

Reviewed Changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
ResponseMapperTests.cs	Added comprehensive unit tests for CompleteMultipartUploadResponse mapping validation
TransferUtilityTests.cs	Added extensive integration tests for multipart upload lifecycle events
MultipartUploadCommand.async.cs	Integrated lifecycle event firing and response mapping in async multipart upload flow
ResponseMapper.cs	Implemented mapping logic from CompleteMultipartUploadResponse to TransferUtilityUploadResponse
MultipartUploadCommand.cs	Added event firing helper methods and enhanced progress tracking
dev config	Added patch-level configuration with appropriate changelog messages

Comments suppressed due to low confidence (1)

sdk/src/Services/S3/Custom/Transfer/Internal/_async/MultipartUploadCommand.async.cs:1

• The UploadProgressArgs constructor call has been modified to include an additional parameter (_fileTransporterRequest). This appears to be a breaking change to the UploadProgressArgs constructor signature. Breaking changes should be avoided in patch releases and require justification or a major version bump.

/*

[Copilot]

The invalid bucket name generation logic is duplicated across multiple test methods. Consider extracting this into a helper method to improve maintainability and ensure consistency.

[Copilot]

The invalid bucket name generation logic is duplicated across multiple test methods. Consider extracting this into a helper method to improve maintainability and ensure consistency.