Pipeline to facilitate Roslyn Copilot publish

[AbhitejJohn]

This pipeline ensures we get the latest roslyn copilot bits. IT needs to be approved explicitly from someone with a SAW, so I've left it as a manual trigger for now. I could imagine a release flow though that auto triggers some of these and that one person with a SAW makes all the approvals needed at once.

Pipeline is here: https://devdiv.visualstudio.com/DevDiv/_build?definitionId=27222

[dibarbet]

Kind of a meta question here. Should this pipeline even be in this repo? Would conversations be a better place?

For example if you want to change the folder name where it finds the conversations build artifacts to upload. Now you have to make the change across two repos. If this was in conversations you just updated both at the same time.

[AbhitejJohn]

Good question, my thinking was having this closer to the component that actually needs it. The conversations repo has a slightly different set of processes tied to build and release pipelines which are tied to VS. Having it here gives us the freedom to iterate on this quicker. It also keeps this in our teams cross hairs a little more working with the processes we have - its been hard figuring out where things exist, so trying to keep some of the infra pieces atleast in fewer places.

[AbhitejJohn]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).