`devops::release` issues without a category label

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

• #11649 (closed) (confidential) ~"(confidential)"
• #11562 (closed) 'Dashboards' dropdown button is missing the chevron (app header) ~"Secure", UI polish, ~"devops::release", frontend
• #11306 (closed) Refactor Empty State Component for Environments and Operations Dashboard to use GitLab UI ~"Release", UI component, ~"backstage", ~"devops::release", frontend, ~"technical debt"
• #9627 (closed) Binary Authorization PoC Deliverable, GitLab Ultimate, ~"Release", ~"devops::release", feature, missed-deliverable, missed:11.10, missed:11.11, missed:11.9, ~"product discovery", ~"workflow::In dev"
• #9441 (closed) Show an environment list from an inputted text on Secret Variables and Feature Flags ~"Accepting merge requests", ~"Release", ~"devops::release", feature
• #9231 (closed) Remove page heading in feature flags empty state ~"Accepting merge requests", ~"Release", UI polish, UX, UX debt, ~"devops::release", frontend
• #9230 (closed) Remove second primary button from feature flags empty state ~"Accepting merge requests", ~"Release", UI polish, UX, UX debt, ~"devops::release", frontend
• #7812 (closed) Move incremental rollouts from CE to EE ~"Accepting merge requests", ~"Release", ~"auto devops", ~"devops::release", feature
• #7789 (closed) Make backend aware of incremental rollout ~"Accepting merge requests", GitLab Premium, ~"Release", backend, ~"devops::release", ~"technical debt"
• #6788 (closed) Gitlab Kubernetes integration pod visualisation is incorrect, when multiple components are deployed ~"Accepting merge requests", ~"P4", ~"Release", ~"S4", ~"bug", ~"devops::release", ~"kubernetes"
• #5582 (closed) Environments API: add missing actions and data to Environments and Deployments APIs ~"Accepting merge requests", ~"Release", api, customer, deploy, ~"devops::release", feature
• #5470 (closed) Reconsider Deploy Boards match criteria ~"Accepting merge requests", ~"Configure", ~"Release", backend, customer, ~"devops::release", feature, frontend
• #5337 Ensure a 2fa step happens between Commit and Deploy ~"Accepting merge requests", ~"Release", ~"devops::release", direction, feature
• #5313 (closed) Creating an environment wildcard is weird ~"Contribute for prize", ~"Release", Stretch, ~"UX ready", backend, ~"devops::release", ~"enhancement", frontend, settings, ~"workflow::In review"
• #2656 (closed) Environment page not updated after deploy job runs ~"Accepting merge requests", ~"Release", UI polish, UX, awaiting feedback, ~"devops::release"
• #2651 Consider making environment name case-insensitive ~"Accepting merge requests", ~"Release", ~"devops::release"
• #2231 (closed) Show pod information ~"Accepting merge requests", ~"Release", deploy, ~"devops::release", feature
• #2217 Deploy messages should be canary-aware ~"Accepting merge requests", ~"Release", UX, deploy, ~"devops::release"
• #2215 (closed) Show related services separately in deploy boards ~"Accepting merge requests", ~"Release", UI polish, UX, ~"devops::release", direction, feature
• #1829 Deeper pod environment status ~"Accepting merge requests", ~"Release", UX, ~"devops::release", feature
• #877 Support GitLab pages with external URL for environments ~"Accepting merge requests", ~"Release", ~"devops::release", feature