CC @xiangyan99 for awareness.

Re-orchestrate conda artifact assembly

• Remove manual test invocations of the conda packages.
• Create a separate pipeline in internal for publishing and package assembly.
• Need to bring integration publishing online all the packages. Doing so will enable tiered update when Xiang is rolling out a set of conda packages. EG: He releases azure-core -> builds and publishes to integration feed. Once that package is available, the other packages that take a dependency (azure-storage for instance) can also be published successfully.
• We should have an established one or two build process (to account for dependencies) that assembles artifacts that Xiang can manually publish to the conda channel.
• Can we modify the user agent strings that the packages use, so we can identify a conda package versus a standard one.

Publish directly to microsoft conda channel

After we work out the final artifacts...

• Explore what happens when you attempt to publish a new package without first going through the new package onboarding with the conda channel. We need the error to be explicit and redirect the dev to the proper place to finish the process.
• Publish to official channel directly from build stage in a approvable release stage.