Enable terminal logger in CI scenarios

[baronfel]

@baronfel are there any plans to invest some more into terminal logger to be active also on CI? Or is this outside of its scope?

In MTP we are using the same ansi logger on local as well as on server, we even use coloring on azdo / github when we can, because it works. We just had to re-think the status bars, they need to render differently because we cannot backtrack cursor in the non-interactive output.

Originally posted by @nohwnd in dotnet/sdk#50572 (comment)

[baronfel]

An update on this - the -tl:on flag can now be used to force the usage of TL even in CI scenarios. This was the intended behavior but we had a bug in the interpretation of that flag. We still need a way to detect/disable the live-update portion independently of other settings, and we may want that feature for LLMs as well so that we don't spam the token context window.

[baronfel]

This is an area where spectre could have automatically solved the problem for us. It has capability probing logic, and in environments that are noninteractive it would render a progress bar as a monotonically-updating bar instead of a spinner or time counter, etc. And/or we could have built on its capability probing and disabled the node progress reporting entirely.