CanInstallRemoteNuGetPackage_LatestVariations failed in CI

[tmat]

https://dev.azure.com/dnceng-public/public/_build/results?buildId=65642&view=ms.vss-test-web.build-test-results-tab&runId=1338148&resultId=100064&paneView=debug

Assert.Equal() Failure\n                                   ↓ (pos 100)\nExpected: ···ojectTemplates.5.0\n\nSuccess: Microsoft.DotNet.Common.ProjectT···\nActual:   ···ojectTemplates.5.0\n\nRetrying 'FindPackagesByIdAsync' for sour···\n                                   ↑ (pos 100)

Stack trace
   at Microsoft.DotNet.Cli.New.IntegrationTests.DotnetNewInstallTests.CanInstallRemoteNuGetPackage_LatestVariations(String commandName) in /Users/runner/work/1/s/src/Tests/dotnet-new.Tests/DotnetNewInstallTests.cs:line 87
   at InvokeStub_DotnetNewInstallTests.CanInstallRemoteNuGetPackage_LatestVariations(Object, Object, IntPtr*)
   at System.Reflection.MethodInvoker.Invoke(Object obj, IntPtr* args, BindingFlags invokeAttr)

[marcpopMSFT]

@dotnet/templating-engine-maintainers to take a look.

[vlada-shubina]

@GangWang01 could you please take a look? thank you

[GangWang01]

From the directory path the test failed on macOS in CI. Retrying 'FindPackagesByIdAsync' for sour··· told Nuget failed to get the package somehow during template installation. Probably it's the same problem as described in #28801 (comment). In CI on macOS Nuget hit the connection issue randomly.

[vlada-shubina]

We decided not to take any action on that. These are random connectivity issues in the images. Any operation interacting with NuGet.org, Azure resources etc. may be affected. Setting up retries on all the tests that may touch external resources are not reasonable, and may not help.

Closing for now, we might want to reopen if the issue will reappear.
Also we drastically decreased number of tests thanks to snapshot testing now, so issues hopefully are less likely.