Split package publishing into separate buckets

To avoid breaking our customers, we need our packages available on nuget.org (or other feeds) in a very specific order. First the various packages for the workloads, then all the manifests (which have manifest in the name), then the workload set which is microsoft.net.workloads.

The idea we had was when doing the publish step we split it into three parts in the pipeline.

The first is all packages that we were going to publish that aren't the manifest or workload set.

Then get in a loop checking if one of those packages is available through the API in the feed we just published to. The idea here is that usually nuget can take minutes to longer to make a newly uploaded package available. Since we might publish ~250 packages, lets pick one and search for it till it's available every five minutes, then the next one. Eventually we validate all 250 but we are only pinging for one at a time.

Once all the pack packages are publish, do the same for the manifest packages. Then publish the workload set.