Update Live Env E2E Pipelines on Pipeline Monitoring Page

Why is this change being made?

This MR updates the live environment E2E test pipelines on the Pipeline Monitoring page to contain the most up-to-date information.

The following changes have been made:

• Added the following existing pipelines that were missing from the documentation:
  • Staging Full tests that run after post-deploy migrations
  • Staging Canary Full tests that run after each Staging Canary deployment, and when a feature flag has been updated to true or 100% in Staging
  • CustomersDot Production Smoke tests that run after each CustomersDot Production deployment
• Removed after a feature flag in production has been updated to *true* or *100%* from the Production entry, and added it to the Canary entry, now that we are targeting Canary when tests are triggered by feature flag changes (changed in Trigger Production Canary Smoke Tests on FF Change)
• Updated and fixed a few incorrect pipeline and definition links

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
  • The when to get approval handbook section explains the workflow in more detail
• For transparency, share this MR with the audience that will be impacted.
  • Team: For changes that affect your direct team, share in your group Slack channel
  • Department: If the update affects your department, share the MR in your department Slack channel
  • Division: If the update affects your division, share the MR in your division Slack channel
  • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
    • For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter

Commits

• Update Live Env E2E Pipelines on Pipeline Monitoring Page

---