Add extension methods to PublishingStep & PublishingTask for direct Complete/Update operations

[Copilot]

This PR adds extension methods to PublishingStep and PublishingTask that allow users to directly perform completion and update operations without needing to manually interact with the IPublishingActivityProgressReporter.

Changes Made

New Extension Methods

Added PublishingExtensions class with the following methods:

For PublishingStep:

• UpdateStatusAsync(string statusText) - Updates the step's status text
• SucceedAsync(string? message) - Completes the step successfully
• WarnAsync(string? message) - Completes the step with a warning
• FailAsync(string? errorMessage) - Completes the step with an error

For PublishingTask:

• UpdateStatusAsync(string statusText) - Updates the task's status text
• SucceedAsync(string? message) - Completes the task successfully
• WarnAsync(string? message) - Completes the task with a warning
• FailAsync(string? errorMessage) - Completes the task with an error

Infrastructure Changes

• Added internal Reporter property to both PublishingStep and PublishingTask to store reference to the creating progress reporter
• Added StatusText property to PublishingStep to support status updates
• Extended IPublishingActivityProgressReporter with UpdateStepAsync method
• Updated both PublishingActivityProgressReporter and NullPublishingActivityProgressReporter to set reporter references and implement the new interface method

Usage Example

// Before: Manual reporter interaction
var step = await reporter.CreateStepAsync("Building images", cancellationToken);
await reporter.UpdateStepAsync(step, "Processing...", cancellationToken);
await reporter.CompleteStepAsync(step, "Build completed", cancellationToken);

// After: Direct extension methods
var step = await reporter.CreateStepAsync("Building images", cancellationToken);
await step.UpdateStatusAsync("Processing...", cancellationToken);
await step.SucceedAsync("Build completed", cancellationToken);

All existing tests continue to pass, and comprehensive tests have been added for the new extension methods.

Fixes #9994.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[captainsafia]

Good start! Remove the StatusText property on PublishingStep and any APIs related to it.

[Copilot]

Good start! Remove the StatusText property on PublishingStep and any APIs related to it.

Done! Removed the StatusText property from PublishingStep and all related APIs including the UpdateStepAsync method and UpdateStatusAsync extension method. The extension methods for completion operations (SucceedAsync, WarnAsync, FailAsync) remain and work correctly. (347e5a7)

[captainsafia]

Add a new API on PublishingStep that will let me create a Task parented to it.

var step = await reporter.CreateStepAsync("Test Step", CancellationToken.None);
var task = await step.CreateTaskAsync("Initial status", CancellationToken.None)

[Copilot]

Add a new API on PublishingStep that will let me create a Task parented to it.

...

Added the CreateTaskAsync extension method to PublishingStep. You can now create tasks directly from steps:

var step = await reporter.CreateStepAsync("Test Step", CancellationToken.None);
var task = await step.CreateTaskAsync("Initial status", CancellationToken.None);

The method includes proper error handling and comprehensive tests. (70d9c39)

[captainsafia]

@copilot Can you update this branch with the latest changes from main and update the AzurePublishingContext, DockerComposePublishingContext, and ResourceContainerImageBuilder to use the new APIs.

[Copilot]

@copilot Can you update this branch with the latest changes from main and update the AzurePublishingContext, DockerComposePublishingContext, and ResourceContainerImageBuilder to use the new APIs...

Updated branch with latest changes from main and updated the AzurePublishingContext, DockerComposePublishingContext, and ResourceContainerImageBuilder to use the new extension methods APIs. All implementations now use the streamlined approach instead of manual reporter interactions. (eee0222)

[captainsafia]

Undo the changes in Aspire.Hosting.Azure and Aspire.Hosting.Docker.

[Copilot]

Undo the changes in Aspire.Hosting.Azure and Aspire.Hosting.Docker.

Changes in Aspire.Hosting.Azure and Aspire.Hosting.Docker have been reverted to their original state. The new extension methods remain available but these components now use the original publishing APIs instead. (c4ce5b1)

[captainsafia]

@davidfowl @mitchdenny This is rebased and ready for review.

[eerhardt]

The ctor is public for this class, but this property is internal...?

[Copilot]

Fixed the accessibility inconsistency by making the Reporter properties public to match the public constructors. This ensures consistent API design where users can create instances directly and all public members are accessible. (173b7cb)

[eerhardt]

Sorry, I meant to make the constructor internal, not make these public.

[Copilot]

Made the constructors internal and restored the Reporter properties to internal access. This ensures proper encapsulation where only the progress reporter implementations can create instances, while the extension methods can still access the Reporter property within the same assembly. (8db3dc5)