Add nuget release yaml pipelines

[jviau]

Issue describing the changes in this PR

resolves #issue_for_this_pr

Pull request checklist

• My changes do not require documentation changes
  • Otherwise: Documentation issue linked to PR
• My changes should not be added to the release notes for the next release
  • Otherwise: I've added my notes to release_notes.md
• My changes do not need to be backported to a previous version
  • Otherwise: Backport tracked by issue/PR #issue_or_pr
• I have added all required tests (Unit tests, E2E tests)

Additional information

Adds release yaml pipelines for all of our nuget packages. These all leverage a template in PR here: https://dev.azure.com/azfunc/internal/_git/engineering/pullrequest/889 (internal only)

Overview

For core & SDK, we have a single pipeline which uses a queue-time selection to release core or sdk. This was done as we intend to eventually merge core and SDK together, which will result in a single release pipeline then anyways.

For all extension packages, there is a pipeline per package.

Selecting the build to be released is done via the queue-time resource selection UI.

Design

These pipelines leverage a template in PR in our internal engineering repo. This template will:

1. Wait for approval via manual validation
2. Publish to internal Azure Devops feed
3. Wait for approval again (this time the pipeline enqueuer can self-approve). This gives an opportunity to validate the packages.
4. Publish to nuget.org one of two ways (depending on parameters provided):
   1. Directly via a nuget service connection
   2. Via Azure SDK partner pipeline (we use this one). The packages will have been uploaded as part of step 2, and this step will run the pipeline. NOTE: the partner pipeline recently added an approval step as well. To release we will need to go to the enqueued build and approve it once more.