[release/10.0.2xx] Update dependencies from microsoft/testfx

[dotnet-maestro]

This pull request updates the following dependencies

From https://github.com/microsoft/testfx

• Subscription: 87866503-65ee-466e-aed8-9efcce1505f7
• Build: 20260113.3 (297152)
• Date Produced: January 13, 2026 9:02:17 PM UTC
• Commit: a92cb454cfad608883388349624bd726a1796f5e
• Branch: main

• Dependency Updates:
  • From 2.1.0-preview.25571.1 to 2.1.0-preview.26063.3
    • Microsoft.Testing.Platform
  • From 4.1.0-preview.25571.1 to 4.1.0-preview.26063.3
    • MSTest

[DonnaChen888]

Updated dependency versions in Version.Details.xml to resolve NU1109 package downgrade error in HotReload tests.
@marcpopMSFT , @nagilson Could you please review and confirm if this approach looks good?

Error:
test/Microsoft.DotNet.HotReload.Watch.Aspire.Tests/Microsoft.DotNet.HotReload.Watch.Aspire.Tests.csproj(0,0): error NU1109: (NETCORE_ENGINEERING_TELEMETRY=Restore) Detected package downgrade: Microsoft.CodeAnalysis.Features from 5.3.0-2.25560.14 to centrally defined 5.3.0-1.25568.105. Update the centrally managed package version to a higher version.
Microsoft.DotNet.HotReload.Watch.Aspire.Tests -> Microsoft.CodeAnalysis.ExternalAccess.HotReload 5.3.0-2.25560.14 -> Microsoft.CodeAnalysis.Features (= 5.3.0-2.25560.14)

[MiYanni]

This PR is showing the same problem described here: #52028 (comment)

The error log will show:

.dotnet/sdk/10.0.100/NuGet.targets(196,5): error : (NETCORE_ENGINEERING_TELEMETRY=Restore) '[]' is not a valid version string.

[nagilson]

This PR is showing the same problem described here: #52028 (comment)

The error log will show:

.dotnet/sdk/10.0.100/NuGet.targets(196,5): error : (NETCORE_ENGINEERING_TELEMETRY=Restore) '[]' is not a valid version string.

I'm not sure how this issue #52028 (comment) is the same. This branch defines hot reload packages in both of the version.details files. That issue in 52028 also manifested as a hot reload error, not as an error in the nuget targets. With that said, it could be an issue with the NuGet packages. However, this only seems to happen on the test fx branches and I'm not seeing it pop up in other PRs, nor did I see this specific error in the history of 52028. This leads me to think it's an issue with the test fx updates.

May you help explain? Do you think fixing the nuget package source will resolve the issue?

[dsplaisted]

@dotnet/dotnet-testing-admin Could someone investigate the dotnet test test failures on this PR?

[Youssef1313]

Probably needs the same change as in #52053 (dc26e67 specifically)

[nagilson]

Thanks, that sounds right. @Youssef1313 May you please have yourself or someone from the testing team look into pushing that?

[SimonZhao888]

@MiYanni, @Youssef1313 there are still 3 test cases failed in our test leg, could you please take a look at the following test cases?

RunTestProjectWithCodeCoverage_ShouldReturnExitCodeGenericFailure
FileBasedApp_CentralPackageManagement_NoVersionSpecified_KeepExisting

[nagilson]

@MiYanni, @Youssef1313 there are still 3 test cases failed in our test leg, could you please take a look at the following test cases?

RunTestProjectWithCodeCoverage_ShouldReturnExitCodeGenericFailure
FileBasedApp_CentralPackageManagement_NoVersionSpecified_KeepExisting

The top is a test issue, the CPM issue is unrelated to this. #52439