fix: update dependency tree in production release pipeline (#2272)

#### Details

Add dependency between different stages of the pipeline to run them
sequentially with 1ES template

##### Motivation

<!-- This can be as simple as "addresses issue #123" -->

##### Context

<!-- Are there any parts that you've intentionally left out-of-scope for
a later PR to handle? -->

<!-- Were there any alternative approaches you considered? What
tradeoffs did you consider? -->

#### Pull request checklist
<!-- If a checklist item is not applicable to this change, write "n/a"
in the checkbox -->
- [ ] Addresses an existing issue: Fixes #0000
- [ ] Added relevant unit test for your changes. (`yarn test`)
- [ ] Verified code coverage for the changes made. Check coverage report
at: `<rootDir>/test-results/unit/coverage`
- [ ] Ran precheckin (`yarn precheckin`)

pipelines/prod-release.yaml

@@ -59,6 +59,7 @@ extends:
                         isProduction: true
 
             - stage: create_release_tag
+              dependsOn: package_publish_staging
               variables:
                   - name: tag
                     value: v${{ parameters.prodVersionOverride }}-sources-ado
@@ -91,6 +92,7 @@ extends:
                               assets: '$(System.DefaultWorkingDirectory)/ado-extension-drop/NOTICE.html'
 
             - stage: package_publish_prod
+              dependsOn: create_release_tag
               variables:
                   - group: a11y-insights-ado-extension-prod
                   - name: extensionVersionOverride