dotnet CDN tracking issue

[richlander]

We are making important changes to the dotnet CND, due to azureedge.net domains no longer being supported/available, per #9671.

The following are the tasks we intend to take on with target timelines. All of this is expected to evolve as we learn more.

Phase 1 (January):

• Remove azureedge.net domains from install script install-scripts#559
• [main] Update .NET download URLs dotnet-docker#6125

Phase 2 (February-March):

• Use CDN domains in releases-index.json #9669
• Use builds.dotnet.microsoft.com CDN in releases.json files #9675
• Use new URIs for latest links arcade#15365
• Publish guidance for using .NET CDNs, install scripts, and other resources for installer/archive acquition #9673
• Deploy install scripts to dotnetcli account install-scripts#558
• Remove "no cdn" concept from install script. install-scripts#563

Phase 3 (April?):

• Disable dotnetcli.azureedge.net and dotnetbuilds.azureedge.net domains #9676

Related:

• Test dotnet CDN Performance #9677
• .NET Install Domains and URLs Update actions/setup-dotnet#570