Disable logging when loading projects in dotnet test

[mariam-abdulla]

This pull request simplifies the handling of MSBuild logging in the MSBuildUtility.cs file by removing the FacadeLogger and its associated logic. The changes streamline the creation of the ProjectCollection object and eliminate unnecessary shutdown operations for the logger.

Simplification of MSBuild logging:

• Removed the FacadeLogger initialization and its shutdown logic in public static (IEnumerable<ParallelizableTestModuleGroupWithSequentialInnerModules method, simplifying the code and ensuring the ProjectCollection is created without a logger. (src/Cli/dotnet/Commands/Test/MSBuildUtility.cs, [1] [2]

[Copilot]

Pull Request Overview

Streamlines MSBuild project loading in dotnet test by removing custom logging and simplifying ProjectCollection creation.

• Removes FacadeLogger initialization and shutdown logic.
• Updates ProjectCollection instantiation to pass null for loggers.

Comments suppressed due to low confidence (1)

src/Cli/dotnet/Commands/Test/MSBuildUtility.cs:35

• Consider adding or updating tests to cover the scenario where logging is disabled, ensuring project loading behaves correctly without the FacadeLogger.

        var collection = new ProjectCollection(globalProperties: CommonRunHelpers.GetGlobalPropertiesFromArgs([.. buildOptions.MSBuildArgs]), null, toolsetDefinitionLocations: ToolsetDefinitionLocations.Default);

[Youssef1313]

Approving as it doesn't work correctly on its current form.

@rainersigwald @YuliiaKovalova We definitely would love if there is a way/workaround to correctly produce a binlog for multiple evaluations/executions