[LiveLogger] Define long-term test plan

[ladipro]

Per @rokonec's work in #8418, the test cases below are designed to give us good enough coverage. Given that this is inherently manual testing, we should figure out who executes them and when/how often.

Test Case	Single Console	Multi project with tests	Orchard	non SDK .NET	non SDK C++
rebuild /m:1	✔️	✔️	✔️	✔️	✔️
rebuild /m	✔️	✔️	✔️	✔️	✔️
rebuild w/ cancel	✔️		✔️
restore	✔️	✔️	✔️
interactive restore	✔️	✔️	✔️
rebuild w/ errors	✔️	✔️	✔️	✔️	✔️
rebuild w/ lots of errors		✔️	✔️
restore w/ errors		✔️
dotnet test		✔️	✔️
test w/ MSBuild server opt in			✔️

I have added dotnet test intuitively, as I know it uses Console colors and Console.Write for test progress reporting.

As for "Multi project with tests" I would recommend sln with one console, three class libraries projects and one test xunit project.

By interactive restore I mean a restore which DeviceFlow prompt:

Here are some simple steps how to prepare simple console app:

• Running installcredprovider per these instructions
• If it was already installed we might need to delete cached credentials from: $env:UserProfile\AppData\Local\MicrosoftCredentialProvider
• If it was built before delete .\bin and .\obj folder

> dotnet new nugetconfig
> dotnet nuget add source https://pkgs.dev.azure.com/dnceng/internal/_packaging/7.0.100-rc.1.22429.3-shipping/nuget/v3/index.json
> dotnet new console
> dotnet build -r win-x64 --interactive --restore

Originally posted by @rokonec in #8418 (comment)

[rainersigwald]

I don't think we're going to do more than the existing acceptance-type tests + automation where we can.