Refactor AzureDevOpsTestResultsPublisher into focused partial classes

[Copilot]

AzureDevOpsTestResultsPublisher.cs had grown into a large mixed-responsibility file, making the live publishing flow harder to navigate and review. This change keeps the type and behavior intact while splitting the implementation into focused partials within the Azure DevOps report extension.

• Split by responsibility

  • Kept the main AzureDevOpsTestResultsPublisher.cs file focused on lifecycle entry points, coordination state, constructors, and public/internal surface area.
  • Moved result construction and attachment shaping into AzureDevOpsTestResultsPublisher.ResultFactory.cs.
  • Moved batching, retry, and upload scheduling into AzureDevOpsTestResultsPublisher.Flush.cs.
  • Moved environment/config resolution and run-name helpers into AzureDevOpsTestResultsPublisher.Configuration.cs.

• Preserved contract and behavior

  • Retained the same sealed type, now marked partial.
  • Kept method names, visibility, and call flow unchanged.
  • Scoped the refactor entirely to src/Platform/Microsoft.Testing.Extensions.AzureDevOpsReport/.

• Result

  • Each partial stays under 300 lines and maps cleanly to one concern, reducing navigation cost and merge pressure on the publisher implementation.

internal sealed partial class AzureDevOpsTestResultsPublisher
{
    public async Task ConsumeAsync(IDataProducer dataProducer, IData value, CancellationToken cancellationToken)
    {
        // lifecycle / coordination remains in the main partial
    }
}

internal sealed partial class AzureDevOpsTestResultsPublisher
{
    internal static AzureDevOpsTestCaseResultWithAttachments? CreateTestCaseResult(TestNode testNode, string automatedTestStorage)
    {
        // result shaping moved into ResultFactory.cs
    }
}

[Copilot]

Copilot wasn't able to review any files in this pull request.