`devops::verify` issues without a category label

Attention @jlenny, @joshlambert @jheimbuck_gl The following issues have been identified in the devops::verify stage that do not have a category label. These should be applied with urgency so that important issues are not being lost track of.

• #14791 (closed) Pipelines must succeed option behavior has changed devopsverify, regression:12.2
• #14778 (closed) Multi-project pipelines: Some predefined variables not passing to downstream project ~"S2", ~"bug", ~"ci variables", customer, devopsverify, reproduced on GitLab.com
• #14734 (closed) Masked variables still visible in the job log for any member role ~"S4", ~"artifacts", ~"bug", devopsverify, ~"group::continuous integration"
• #14688 (closed) Runner system failure ~"P1", ~"S1", auto updated, devopsverify, grouprunner, master:broken, ~"master:flaky"
• #13369 (closed) List public projects in Usage Quotas page ~"GitLab Enterprise Edition", devopsverify, grouprunner
• #12379 Expose an API for getting CI minutes ~"Accepting merge requests", ~"Category:Account Management", ~"GitLab Enterprise Edition", ~"P4", ~"S4", UX, backend, devopsverify, gitlab.com, grouprunner
• #7446 (closed) Switch from flat group runner minutes to X per-member ~"Accepting merge requests", ~"GitLab Enterprise Edition", ~"Pricing", devopsverify, ~"group::upsell"