Update .NET SDK to 10.0.100-alpha.1.25067.4

[github-actions]

Updates the .NET SDK to version 10.0.100-alpha.1.25063.8, which also updates the .NET runtime from version 10.0.0-alpha.1.25052.4 to version 10.0.0-alpha.1.25062.3.

This pull request was auto-generated by GitHub Actions.

[dotnet-policy-service]

Auto-approving SDK update.

[wtgodbe]

❌.dotnet\sdk\10.0.100-alpha.1.25063.8\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.ApiCompat.ValidatePackage.targets(39,5): error CP1002: Could not resolve reference 'System.ServiceModel.Internals.dll' in any of the provided search directories.
❌.dotnet\sdk\10.0.100-alpha.1.25063.8\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.ApiCompat.ValidatePackage.targets(39,5): error CP1002: Could not resolve reference 'SMDiagnostics.dll' in any of the provided search directories.
❌.dotnet\sdk\10.0.100-alpha.1.25063.8\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.ApiCompat.ValidatePackage.targets(39,5): error CP1002: Could not resolve reference 'Microsoft.NET.StringTools.dll' in any of the provided search directories.

@carlossanlop @ViktorHofer looks like you guys have been touching APICompat over the past week or so, does this failure look familiar? dotnet/sdk#45807

[carlossanlop]

@carlossanlop @ViktorHofer looks like you guys have been touching APICompat over the past week or so, does this failure look familiar? dotnet/sdk#45807

I'll take a closer look at my change but it basically just made changes around logging. No other behaviors should've changed.

[carlossanlop]

Okay, one change we made was to stop logging CP1002, which is the error shown in this issue:

https://github.com/dotnet/sdk/pull/45807/files#diff-9b4f11ad017bb8ab9b999da096d137319060b5f14c81c170f4404df7568ea9c5

- // Assembly loading ids
-        public const string AssemblyReferenceNotFound = "CP1002";

@ViktorHofer should we bring this back? That removal was part of the extra suggestions in the PR.

[ViktorHofer]

Yes, the failure is from dotnet/sdk#45807 and need a reaction here. We intentionally made a breaking change as CP1002 warnings didn't make sense to include in the suppression file. I'll push a commit.

[ViktorHofer]

I submitted dotnet/sdk#46059 to fix this in a better way. .NET Framework has a set of dangling internal only assemblies that should never get loaded. The PR is taking care of that so that our customers won't these false positives as well.

Meanwhile, I pushed a commit to suppress the CP1002 diagnostics.

[wtgodbe]

Thanks!

[ViktorHofer]

Needs another SDK update

[ViktorHofer]

I don't understand why this new CP1002 is suddenly showing up. I will debug this offline.

[wtgodbe]

Thanks @ViktorHofer!