QA issue should be an independent job of the coordinated pipeline

Context

The current deployment order of the coordinated pipeline looks like this:

gstg-ref \
          ---> gstg ---> gprd-cny ---> gprd
gstg-cny /

QA issues are created during a gstg deployment, particularly when the gstg-track job is executed. This QA issue is used by Quality on the test reports for informational and debugging purposes (example). With &608 (closed) and gitlab-org&6401 (closed), we now have multiple staging environments that trigger QA and generate tests reports that also need to reference the QA issue. This is not possible with the current order: deployments for gstg-ref and gstg-cny are triggered before the deployment to gstg, so by the time they reference the QA issue, this one hasn't been created yet.

Proposal

Let's make the generation of QA issue an independent job in the coordinated pipeline by creating it before deploying to any environment:

                  / gstg-ref \
QA issue creation             ---> gstg ---> gprd-cny ---> gprd
                  \ gstg-cny /

Milestones

Edited by John Skarbek