Respect console logger verbosity from a settings file
Fixes #10369
dotnet test --settings my.runsettings ignored the <Verbosity> configured for the console logger and always ran at the MSBuild-derived verbosity.
Two things caused it. The MSBuild VSTestTask appended --logger:Console;Verbosity=<msbuild verbosity> even when the settings file configured the console logger, and LoggerUtilities.AddLoggerToRunSettings then rebuilt the logger entry from that argument, dropping the Configuration the settings file had supplied.
VSTestTask now leaves Verbosity= off only when the settings file actually configures Configuration/Verbosity for the console logger; otherwise the MSBuild verbosity is injected as before. VSTestTask2 is unaffected ā the MSBuild logger's verbosity is driven by MSBuild rather than user settings, so it always receives it.
AddLoggerToRunSettings now reuses the entry already present in LoggerRunSettings instead of constructing a replacement, so Configuration, codeBase and assemblyQualifiedName survive. Whatever the command line spells out still wins, and naming a logger there enables it even if the settings file disabled it.
Verified: Microsoft.TestPlatform.Build.UnitTests and vstest.console.UnitTests pass on net481 and net11.0 from a Release build.
š¤