`devops::release` issues without a category label

Attention @ogolowinski, 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.

• - #36967 (closed) Validate the SHA and branch name of a deployment before creating it ~"Accepting merge requests", ~"bug", deploy, ~"devops::release", ~"group::release management"
• - #36848 Only shows jobs relevant to environment under operations ~"devops::release", environments, feature, ~"group::release management"
• - #36824 (closed) Transient failure in qa/specs/features/ee/browser_ui/6_release/pipelines_for_merged_results_and_merge_trains_spec.rb:53 QA, Quality, ~"S1", ~"bug", ~"devops::release", found:in MR
• - #36707 (closed) Releases GUI only last 20 releases ~"S3", ~"bug", ~"devops::release", ~"group::release management"
• - #36667 (closed) Add release count to project homepage ~"devops::release", feature, ~"group::release management"
• - #36654 (closed) Docs: move environments doc into correct dir ~"Accepting merge requests", ~"Good for 1st time contributors", Technical Writing, ~"devops::release", docs-technical-debt, documentation, environments
• - #36648 (closed) Creating deployments may lead to Deployments::SuccessWorker running twice ~"Accepting merge requests", deploy, ~"devops::release", ~"group::release management"
• - #36304 (closed) Failure in qa/specs/features/browser_ui/6_release/deploy_key/clone_using_deploy_key_spec.rb QA, Quality, ~"S1", ~"bug", ~"devops::release", found:nightly
• - #35398 (closed) Review 12.5 Release feature doc requirement needs Technical Writing, ~"devops::release", docs-missing
• - #35022 (closed) Move models from EE to core code ~"devops::release", ~"group::progressive delivery", single codebase