Refactor JUnitReport to reuse shared report helper implementations

[Copilot]

JUnitReportEngine had local copies of report filename sanitization, target framework moniker resolution, template-based filename resolution, and the retry timeout already defined in SharedExtensionHelpers. This change removes that drift risk by wiring JUnitReport to the same shared implementations already used by sibling report extensions.

• Align JUnitReport with shared helper usage

  • Link ReportFileNameHelper, ReportFileNameSanitizer, TargetFrameworkMonikerHelper, and ReportFileWriterHelper into Microsoft.Testing.Extensions.JUnitReport.csproj
  • Replace JUnit-local helper implementations with direct calls to the shared helpers

• Remove duplicate logic from JUnitReportEngine

  • Drop the private copies of:
    • filename sanitization / reserved-name handling
    • TFM resolution
    • template resolution + sanitization
  • Replace the hardcoded retry timeout with ReportFileWriterHelper.FileWriteRetryTimeout

• Extend parity coverage

  • Add JUnitReport to the existing cross-extension filename sanitization consistency test so Trx/Html/JUnit stay aligned on sanitizer behavior

private string ResolveXmlFileName(string template)
{
    string processName = Path.GetFileNameWithoutExtension(_testApplicationModuleInfo.GetCurrentTestApplicationFullPath());
    string processId = _environment.ProcessId.ToString(CultureInfo.InvariantCulture);
    return ReportFileNameHelper.ResolveAndSanitize(template, processName, processId, _clock.UtcNow);
}

[Copilot]

Pull request overview

This pull request refactors the Microsoft.Testing.Extensions.JUnitReport extension to reuse the shared report helper implementations already used by other report extensions, reducing duplicated logic and drift risk across extensions.

Changes:

• Linked shared helpers into Microsoft.Testing.Extensions.JUnitReport.csproj (filename templating/sanitization, TFM moniker resolution, and retry timeout constant).
• Updated JUnitReportEngine to call the shared helpers instead of maintaining private duplicate implementations.
• Extended the cross-extension sanitizer parity unit tests to include JUnitReport.

Show a summary per file

File	Description
test/UnitTests/Microsoft.Testing.Extensions.UnitTests/ReportFileNameSanitizationConsistencyTests.cs	Adds Trx vs JUnit sanitizer parity validation via reflection to keep behavior aligned across extensions.
test/UnitTests/Microsoft.Testing.Extensions.UnitTests/Microsoft.Testing.Extensions.UnitTests.csproj	Adds a project reference to the JUnitReport extension so the parity test can access JUnitReportEngine.
src/Platform/Microsoft.Testing.Extensions.JUnitReport/Microsoft.Testing.Extensions.JUnitReport.csproj	Links shared helper source files from SharedExtensionHelpers into the JUnitReport project.
src/Platform/Microsoft.Testing.Extensions.JUnitReport/JUnitReportEngine.cs	Replaces local helper logic with calls to shared helpers and uses the shared retry timeout constant in the error path.

Copilot's findings

• Files reviewed: 4/4 changed files
• Comments generated: 0

[Evangelink]

@copilot resolve the merge conflicts in this pull request

[Copilot]

@copilot resolve the merge conflicts in this pull request

Merge conflicts are resolved in commit 31e0f0f. I reconciled Microsoft.Testing.Extensions.JUnitReport.csproj so it keeps the shared-helper refactor and includes the new validator entry from main.