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

• - #35926 (closed) When creating a deployment and linking merge requests, a SQL timeout can prevent the MRs from being linked while the deployment still exists ~"Accepting merge requests", Delivery, ~"bug", deploy, ~"devops::release", ~"group::release management"
• - #35893 (closed) Support binary-type (package) asset for Releases ~"devops::release", feature, ~"group::release management"
• - #35844 Proposal: Add a hint about set up DB_INITIALIZE and DB_MIGRATE into Deploy job log backend, creator-pairing, ~"devops::release", feature, pipeline
• - #35788 (closed) Assets are not show up to guests on the release page. ~"bug", ~"devops::release"
• - #35763 (closed) Consider raising an error in Deployments::UpdateService when using an unsupported status ~"Accepting merge requests", Delivery, ~"backstage", deploy, ~"devops::release", ~"group::release management"
• - #35741 Add UI support for displaying merge requests deployed in a deployment ~"Accepting merge requests", Delivery, UX, deploy, ~"devops::release", feature, frontend, ~"group::release management"
• - #35739 (closed) Add API support for retrieving merge requests deployed in a deployment ~"Accepting merge requests", Delivery, deploy, ~"devops::release", feature, ~"group::release management"
• - #35726 (closed) Reduce cross references in merge train docs ~"devops::release", documentation, ~"group::progressive delivery"
• - #35711 (closed) Persist creater of environments ~"devops::release", ~"group::progressive delivery", permissions, ~"technical debt"
• - #35646 Linking merge requests to deployments may lead to duplicate key errors when changing the status back and forth to success ~"Accepting merge requests", Delivery, deploy, ~"devops::release", ~"group::release management"
• - #35628 (closed) Merge Trains should support fast forward merge Enterprise Edition, GitLab Premium, ~"devops::release", feature, ~"group::progressive delivery"
• - #35556 Follow-up from "Add Unleash Client Settings to gitlab.yml.example" ~"Release [DEPRECATED]", backend, ~"devops::release", feature, missed:12.4, ~"technical debt"
• - #35458 (closed) Expose manual actions, retry path for deployment footer backend, ~"devops::release"
• - #35457 (closed) Evidence collection for releases: make data available to the frontend backend, ~"devops::release"
• - #35398 (closed) Review 12.5 Release feature doc requirement needs Technical Writing, ~"devops::release"
• - #35198 (closed) Merge request diffs.json performs poorly in projects with many deployed environments ~"bug", customer, ~"devops::release", environments, groupsource code, merge requests, ~"performance"
• - #35022 (closed) Move models from EE to core code ~"devops::release", ~"group::progressive delivery", single codebase