DOTNET_SKIP_FIRST_TIME_EXPERIENCE is replaced by DOTNET_NOLOGO

[am11]

Since dotnet sdk 3.1.300 (https://github.com/dotnet/sdk/issues/3828), DOTNET_SKIP_FIRST_TIME_EXPERIENCE was replaced by DOTNET_NOLOGO. NuGet is using the old variable and expecting certain behavior https://github.com/NuGet/NuGet.Services.EndToEnd/blob/91bb0b9269827f75c3a3265e6ccd684d9d665b7f/src/NuGet.Services.EndToEnd/Support/Clients/DotNetExeClient.cs#L63-L67:

            // New installation of DOTNET invokes first time user experience which involves caching, decompressing packages etc.
            // This prevents faster package build times, disable this behavior using environment variable
            var environmentVariables = new Dictionary<string, string>
            {
                { "DOTNET_SKIP_FIRST_TIME_EXPERIENCE", "1" }
            };

but the variable is ignored by all the current (non-EOL) SDK versions.

I'm filing this issue to keep track of the change, but I'm not sure how the actual change would look like. Should it be just removed or replaced by DOTNET_NOLOGO? Is there any replacement for the expected caching behavior (--debug:ephemeral-hive, --debug:virtual-hive maybe)?

cc @baronfel, @ViktorHofer it is also documented: https://github.com/dotnet/docs/blob/923b2a7dc5a9367fc8bf1067f16694416a12a9a8/docs/core/tools/dotnet-environment-variables.md#dotnet_skip_first_time_experience, so once we clarified, we can update the docs accordingly.

[ghost]

Issue is missing Type label, remember to add a Type label

[zivkan]

The repo readme for the NuGet.Services.EndToEnd clearly state it's for automated tests for nuget.org, so I expect that there's no product impact. Moving this to the server team issue tracker.