`devops::release` issues without a category label

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

• - #38259 New tags might not respect the associated SHA of a pipeline ~"devops", ~"devops::release", ~"group::release management", workflowvalidation backlog
• - #38252 (closed) Add development seed data for Release and Merge Train objects development guidelines, ~"devops::release", feature
• - #38000 (closed) When linking merge requests to deployments, we should link for deployments with a status other than "success" ~"Accepting merge requests", ~"S4", ~"bug", deploy, ~"devops::release", ~"group::release management", teamDelivery
• - #37989 (closed) Refactor deployment view button & stop button ~"devops::release", frontend, ~"technical debt"
• - #37947 (closed) When a pipeline fails, manual build & deploy jobs are cancelled even if not triggered by anyone ~"S3", ~"bug", ~"devops::release", ~"group::progressive delivery"
• - #37266 (closed) Gitlab realease api, milestone not found ~"S3", api, ~"bug", ~"devops::release", ~"group::release management", milestones
• - #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