always print auth messages in TL, regardless of verbosity

[baronfel]

Part of dotnet/sdk#47602

Context

With NuGetInteractive=true being passed in more scenarios as of dotnet/sdk#47226, the default verbosity for dotnet run is now minimal for user-present scenarios - that's gross.

Changes Made

Broadly what I'm trying to do here is not require passing -v m to loggers to get the authentication-related messages. Right now dotnet run does this and it's quite noisy compared to previous behavior. This changed because recently I made the SDK start passing --interactive when the user is at the keyboard (similar logic to Terminal Logger's own enablement), and dotnet run has logic to force verbosity to minimal when that happens so that the auth messages print where a user can see them.

I kind of think of auth messages as messages that we should write regardless of verbosity (like errors are), so this is a step down that path for TL.

This change ensures that auth messages are always written in the TL experience, as immediate messages.

If this is accepted, then the SDK could remove the special case it currently has.

Testing

Updated snapshot baselines, manual testing.

Notes

[SimaTian]

Looks good, however this is probably worth looking into.

[baronfel]

@SimaTian I finally got my brain to work and fixed the implementation to no longer lose those valuable warnings. Mind a re-review?

Change addressed