Fix components-e2e logging issues

[MackinnonBuck]

Since #54483 was merged, logs for the components-e2e pipeline has increased to 600MB+ in size on successful runs. Furthermore, there have been multiple recent failures in that pipeline with the following stack trace:

/home/vsts/work/1/s/.dotnet/sdk/9.0.100-preview.3.24161.2/Microsoft.TestPlatform.targets(46,5): error MSB4018: The "VSTestTask2" task failed unexpectedly. [/home/vsts/work/1/s/src/Components/test/E2ETest/Microsoft.AspNetCore.Components.E2ETests.csproj]
/home/vsts/work/1/s/.dotnet/sdk/9.0.100-preview.3.24161.2/Microsoft.TestPlatform.targets(46,5): error MSB4018: System.IndexOutOfRangeException: Index was outside the bounds of the array. [/home/vsts/work/1/s/src/Components/test/E2ETest/Microsoft.AspNetCore.Components.E2ETests.csproj]
/home/vsts/work/1/s/.dotnet/sdk/9.0.100-preview.3.24161.2/Microsoft.TestPlatform.targets(46,5): error MSB4018:    at Microsoft.TestPlatform.Build.Tasks.VSTestTask2.LogEventsFromTextOutput(String singleLine, MessageImportance messageImportance) in /_/src/Microsoft.TestPlatform.Build/Tasks/VSTestTask2.cs:line 67 [/home/vsts/work/1/s/src/Components/test/E2ETest/Microsoft.AspNetCore.Components.E2ETests.csproj]
/home/vsts/work/1/s/.dotnet/sdk/9.0.100-preview.3.24161.2/Microsoft.TestPlatform.targets(46,5): error MSB4018:    at Microsoft.Build.Utilities.ToolTask.LogMessagesFromStandardErrorOrOutput(Queue dataQueue, ManualResetEvent dataAvailableSignal, MessageImportance messageImportance, StandardOutputOrErrorQueueType queueType) [/home/vsts/work/1/s/src/Components/test/E2ETest/Microsoft.AspNetCore.Components.E2ETests.csproj]
/home/vsts/work/1/s/.dotnet/sdk/9.0.100-preview.3.24161.2/Microsoft.TestPlatform.targets(46,5): error MSB4018:    at Microsoft.Build.Utilities.ToolTask.HandleToolNotifications(Process proc) [/home/vsts/work/1/s/src/Components/test/E2ETest/Microsoft.AspNetCore.Components.E2ETests.csproj]
/home/vsts/work/1/s/.dotnet/sdk/9.0.100-preview.3.24161.2/Microsoft.TestPlatform.targets(46,5): error MSB4018:    at Microsoft.Build.Utilities.ToolTask.ExecuteTool(String pathToTool, String responseFileCommands, String commandLineCommands) [/home/vsts/work/1/s/src/Components/test/E2ETest/Microsoft.AspNetCore.Components.E2ETests.csproj]
/home/vsts/work/1/s/.dotnet/sdk/9.0.100-preview.3.24161.2/Microsoft.TestPlatform.targets(46,5): error MSB4018:    at Microsoft.Build.Utilities.ToolTask.Execute() [/home/vsts/work/1/s/src/Components/test/E2ETest/Microsoft.AspNetCore.Components.E2ETests.csproj]
/home/vsts/work/1/s/.dotnet/sdk/9.0.100-preview.3.24161.2/Microsoft.TestPlatform.targets(46,5): error MSB4018:    at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute() [/home/vsts/work/1/s/src/Components/test/E2ETest/Microsoft.AspNetCore.Components.E2ETests.csproj]
/home/vsts/work/1/s/.dotnet/sdk/9.0.100-preview.3.24161.2/Microsoft.TestPlatform.targets(46,5): error MSB4018:    at Microsoft.Build.BackEnd.TaskBuilder.ExecuteInstantiatedTask(ITaskExecutionHost taskExecutionHost, TaskLoggingContext taskLoggingContext, TaskHost taskHost, ItemBucket bucket, TaskExecutionMode howToExecuteTask) [/home/vsts/work/1/s/src/Components/test/E2ETest/Microsoft.AspNetCore.Components.E2ETests.csproj]

Disabling the new TerminalLogger (which is on by default in .NET 9) seems to have resolved both the log size and test pipeline failure issues.

[MackinnonBuck]

cc @nohwnd - it looks like the exception originates from here. Do you think this may be due to the changes in microsoft/vstest#4877?

[nohwnd]

@MackinnonBuck I am having a look, I will put more info in this issue if needed microsoft/vstest#4938. The log size increase is because we are writing all captured outputs from passed tests. This is different from before, where by default we don't write passed tests at all. I though this would be useful, but its probably more problems than gains, will revert.

Then index problem I will have to debug, some info is missing there, and the code is not particularly robust.