Add multipartupload lifecycle tracking

[GarrettBeatty]

Stacked PRs:

• Add OpenStreamResponse mapping #4064
• Add DownloadResponse mapping #4063
• Add UploadWithResponseAsync API #4062
• ->Add multipartupload lifecycle tracking #4061

---

Description

This change adds progress listeners for "initiated", "complete", and "failed" lifecycle events for the MultiUploadCommand. Consumers can subscribe to these callbacks to receive notifications when a simple upload starts, finishes successfully, or fails. this is similar to #4059 but for multi part upload command.

Example usage

// Create a TransferUtilityUploadRequest
TransferUtilityUploadRequest request = new TransferUtilityUploadRequest();

// Subscribe to the progress events
request.UploadInitiatedEvent += Request_UploadInitiatedEvent;
request.UploadCompletedEvent += Request_UploadCompletedEvent;
request.UploadFailedEvent += Request_UploadFailedEvent;

// Use the Transfer Utility to upload the file
using (var transferUtility = new TransferUtility(s3Client))
{
    transferUtility.UploadAsync(request);
}

private void Request_UploadInitiatedEvent(object sender, UploadInitiatedEventArgs e)
{
    Console.WriteLine($"Upload initiated for file: {e.FilePath}");
    Console.WriteLine($"Total bytes to transfer: {e.TotalBytes}");
}

private void Request_UploadCompletedEvent(object sender, UploadCompletedEventArgs e)
{
    Console.WriteLine($"Upload completed for file: {e.FilePath}");
    Console.WriteLine($"Transferred bytes: {e.TransferredBytes}");
    Console.WriteLine($"ETag: {e.Response.ETag}");
    Console.WriteLine($"Version ID: {e.Response.VersionId}");
}

private void Request_UploadFailedEvent(object sender, UploadFailedEventArgs e)
{
    Console.WriteLine($"Upload failed for file: {e.FilePath}");
    Console.WriteLine($"Transferred bytes: {e.TransferredBytes} / {e.TotalBytes}");
}

Motivation and Context

1. To adhere to the SEP

Testing

1 .84f23e9a-f014-44a6-b129-5d10e7aea8d6 - pass
2. Integration tests

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 multipart upload event lifecycles to the AWS S3 Transfer Utility, enabling tracking of upload initiation, completion, and failure events during multipart uploads.

• Adds lifecycle event firing (initiated, completed, failed) to the multipart upload command
• Implements comprehensive integration tests for all event scenarios including unseekable streams
• Includes proper dev config for patch-level changes

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 5 comments.

File	Description
MultipartUploadCommand.async.cs	Adds event firing for transfer lifecycle events during async multipart uploads
MultipartUploadCommand.cs	Implements helper methods to fire transfer lifecycle events and updates progress callback signature
TransferUtilityTests.cs	Adds comprehensive integration tests for multipart upload lifecycle events
433a9a6d-b8ea-4676-b763-70711e8288e3.json	Dev config file specifying patch-level changes with appropriate changelog messages

[Copilot]

Potential null reference exception when initResponse is null. The code should check if initResponse is not null before accessing UploadId, or pass initResponse?.UploadId to handle the null case properly.

Suggested change

	Cleanup(initResponse.UploadId, pendingUploadPartTasks);
	Cleanup(initResponse?.UploadId, pendingUploadPartTasks);

[GarrettBeatty]

not sure if this is needed because initresponse could only be null if the initial request failed and if it did we throw exception above?

[GarrettBeatty]

we are also adding the request object to the progress args as part of this change