Make microsoft/go available as Azure Artifacts Universal Packages

• https://docs.microsoft.com/en-us/azure/devops/artifacts/quickstarts/universal-packages?view=azure-devops
• https://docs.microsoft.com/en-us/azure/devops/pipelines/artifacts/universal-packages?view=azure-devops&tabs=yaml

Example: https://msazure.visualstudio.com/ContainerPlatform/_artifacts/feed/ContainerPlat/UPack/go-windows-amd64

This type of artifact would let people download our bits to a location on the machine with a built-in task, without manual unzip/untar. It looks like it would also be a way to do auto-update. It doesn't appear to set up PATH or have any hooks that would let us do that--the build still has to know where in the artifact go would be located.

It looks like in the internal AzDO project, we can create a feed that is accessible to anyone in the AAD associated with the project. Or, we can potentially create the feed on the public AzDO instance, for all. We'll have to talk with the engineering team about this. AFAIK, Universal Packages haven't been used by .NET teams, and there have recently been a lot of changes happening with the public instance.

We've been asked about this way of getting artifacts a few times, but so far it hasn't been a blocker for any team in particular.

Start with the linked Azure Artifacts Universal Packages documentation and the ContainerPlatform example feed. Confirm with the engineering team whether the package should use an internal or public feed and how access should work. Done means the Microsoft Go artifacts are available through the chosen feed without requiring manual archive extraction; no repository files or tests are named.