Update Ops Section YAML with implementation status

Why is this change being made?

This MR updates Ops Section YAML with the following changes:

• Combines instrumentation.level with implementation.status as per changes in Combine instrumentation_level with implementation_status. !63687 (merged) (merged)
• I've gone through each of the PIs and have assigned it an implementation.status based off the latest status in the linked URLs
• I've also made minor changes listed below in the changes_made column

section.stage.group	primary pi name	implementation status	changes made
ops	Ops - Section TMAU - Sum of Ops Section SMAU	Dashboard	Moved to Dashboard status for Paid/All and SM/SaaS breakouts.
ops.verify	Verify, Verify:CI, Verify:Pipeline Authoring, Verify:Runner - SMAU, GMAU - Unique users triggering pipelines	Dashboard	Moved to Dashboard status for Paid/All and SM/SaaS breakouts.
ops.verify.continuous_integration	Verify, Verify:CI, Verify:Pipeline Authoring, Verify:Runner - SMAU, GMAU - Unique users triggering pipelines	Dashboard	Moved to Dashboard status for Paid/All and SM/SaaS breakouts.
ops.verify.pipeline_authoring	Verify, Verify:CI, Verify:Pipeline Authoring, Verify:Runner - SMAU, GMAU - Unique users triggering pipelines	Dashboard	Moved to Dashboard status for Paid/All and SM/SaaS breakouts.
ops.verify.runner	Verify, Verify:CI, Verify:Pipeline Authoring, Verify:Runner - SMAU, GMAU - Unique users triggering pipelines	Dashboard	Moved to Dashboard status for Paid/All and SM/SaaS breakouts.
ops.verify.testing	Verify:Testing - Paid GMAU - Count of active paid testing feature users	Instrumentation	Moved to Instrumentation status as we need SM instrumentation.
ops.package	Count of users publishing/installing packages	Instrumentation	Moved to Instrumentation as work is in progress for 13.5
ops.package.package	Count of users publishing/installing packages	Instrumentation	Moved to Instrumentation as work is in progress for 13.5
ops.release	Count of users triggering deployments using GitLab	Complete	Moved to Complete status.
ops.release.progressive_delivery	Count of users triggering deployments using GitLab	Complete	Moved to Complete status.
ops.release.release_management	Count of users triggering deployments using GitLab	Complete	Moved to Complete status.
ops.configure	Proxy user count based on attached clusters	Dashboard	Moved to Dashboard status for Paid/All and SM/SaaS breakouts.
ops.configure.configure	Proxy user count based on attached clusters	Dashboard	Moved to Dashboard status for Paid/All and SM/SaaS breakouts.
ops.monitor	Proxy user count based on prometheus integration	Dashboard	Moved to Dashboard status for Paid/All and SM/SaaS breakouts.
ops.monitor.health	Unique users that interact with Alerts and Incidents	Dashboard	Moved to Dashboard status for Paid/All and SM/SaaS breakouts.

• Verify:Runner - Other - Linux Shared (SaaS) Runners Minutes Used, Verify:Runner - Other - Windows Shared Runners (SaaS) Minutes Used, Verify:Runner - Other - Total downloads of runner binaries and docker images per month for self-managed changed to is_primary false. We can only have one primary PI per group. I suggest we combine the above into a single metric for both SM and SaaS or continue using Verify, Verify:CI, Verify:Pipeline Authoring, Verify:Runner - SMAU, GMAU - Unique users triggering pipelines for the time being.
• Verify:Pipeline Authoring - GMAU - Average time to first green pipeline changed to is_primary false. Temporarily switched to using Verify, Verify:CI, Verify:Pipeline Authoring, Verify:Runner - SMAU, GMAU - Unique users triggering pipelines while this is being instrumented.

Also the following non-primary PI changes were made:

• Package:Package - Other - Packages published/installed using the Package Registry moved status to Complete
• Package:Package - Paid GMAU - Count of paid users using the Dependency Proxy moved status to Instrumentation
• Package:Package - AMAU - Count of users publishing packages moved status to Instrumentation
• Package:Package - AMAU - Count of users installing packages moved status to Instrumentation
• Release:Release Management - AMAU - Unique user count viewing Release and Environment pages moved status to Complete
• Release:Progressive Delivery:Feature Flags - AMAU - Unique users triggering feature flag toggles moved status to Instrumentation
• Release:Progressive Delivery:Continuous Delivery - AMAU - Unique users triggering pipelines with automatic deployments (no manual jobs) moved status to Instrumentation
• Release:Progressive Delivery:Review Apps - AMAU - Unique users triggering pipelines that created a review app moved status to Instrumentation
• Release:Progressive Delivery:Advanced Deployments - AMAU - Count of unique users using Canary or Incremental Rollout moved status to Instrumentation
• Release:Progressive Delivery:Deployment to AWS - AMAU - Count of users using AutoDevOps or Ci templates to deploy to AWS moved status to Instrumentation
• Configure:Configure - AMAU - Number of projects with GitLab Managed Terraform State moved to Complete
• Configure:Configure - AMAU - Number of Gitlab Kubernetes Agent instances moved to Data Availability
• Configure:Configure - Other - Number of CI/CD pipeline runs going through our infrastructure management deployment oriented features moved to Target
• Monitor - AMAU - Count of users creating incidents moved to Complete
• Monitor:APM (Legacy) - Other - Total unique users that view metrics or logs moved to Target

Author Checklist

• Provided a concise title for the MR
• Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
• Assign this change to the correct DRI
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
  • 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.
  • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files.