`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.

• #35398 (closed) Review 12.5 Release feature doc requirement needs Technical Writing, ~"devops::release"
• #35355 (closed) Document new "edit release" page ~"devops::release", docs-only, documentation
• #35311 (closed) Review App URL outputs html downloaded file not redirect to Environment URL Alliances, ~"devops", ~"devops::release", workflowvalidation backlog
• #35210 (closed) NoMethodError: undefined method `head_commit_sha' for nil:NilClass ~"bug", ~"devops::release"
• #35166 (closed) Handbook can be slow to merge with merge trains ~"Merge Trains", ~"devops::release"
• #35140 (closed) Stop exposing MR refs in favor of persistent pipeline refs ~"devops::release", ~"technical debt"
• #35135 (closed) Users cannot re-add merge request to a merge train when "pipeline must succeed" is enabled ~"P3", ~"S3", UX, ~"bug", ~"devops::release"
• #35132 (closed) (confidential) ~"(confidential)"
• #35115 (closed) Create dynamic frontend test fixture for releases ~"backstage", ~"devops::release", frontend, ~"group::release management", ~"technical debt", test
• #35022 (closed) Move models from EE to core code ~"devops::release", ~"group::progressive delivery", single codebase
• #34799 (closed) Research and Implementation plan for Limit pipeline concurrency using named semaphores Deliverable, ~"devops::release", ~"group::progressive delivery", planning priority, workflowready for development