pipelines: Unable to publish extensions that use proposed api

[alexweininger]

Problem: the App Service extension uses proposed api and our release pipeline doens't support that. I had to make some changes for a one off release main...alex/release-allow-proposed-api

In order to publish extensions that use proposed apis with vsce you need to specify flags:

  --allow-proposed-apis <apis...>  Allow specific proposed APIs
  --allow-all-proposed-apis        Allow all proposed APIs

But I don't think we want to pass the --allow-all-proposed-apis on all publishes, and I'm not sure if that will even work if extensions don't use proposed api.

[bwateratmsft]

This may eventually be needed for the GitHub Copilot for Azure extension, we'll see.

[alexweininger]

I spent a day or two a few weeks ago trying to be able to pass in flags from the template consumers as parameters to the vsce publish command and I never got it working. If you need this I'll spend some more time on it. Maybe the --allow-all... will work.

[bwateratmsft]

I'll let you know if we plan on releasing with proposed APIs, so far we haven't.