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

• - #36529 (closed) Remove :release_issue_summary feature flag ~"devops::release", ~"group::release management"
• - #36528 (closed) Remove :release_search_filter feature flag Deliverable, ~"backstage", ~"devops::release", ~"group::release management", workflowready for development
• - #36527 (closed) Remove :release_edit_page feature flag Deliverable, ~"backstage", ~"devops::release", feature flag, ~"group::release management", workflowready for development
• - #36498 (closed) Remove feature flag deployment_merge_requests_widget once the changes have been confirmed to work well ~"devops::release", feature flag, ~"group::release management"
• - #36443 Rework parallel merge trains concurrency ~"devops::release", ~"technical debt"
• - #36409 (closed) Add Alerts to Environment Dashboard ~"Accepting merge requests", Enterprise Edition, GitLab Premium, backend, ~"devops::release", feature, frontend
• - #36406 Add UI support for displaying merge requests deployed in a deployment - Deployment View ~"Accepting merge requests", Delivery, UX, deploy, ~"devops::release", feature, frontend, ~"group::release management"
• - #36349 (closed) Add missing empty state for Deploy Keys UI polish, UX, admin dashboard, ~"devops::release", ~"group::release management"
• - #36304 (closed) Failure in qa/specs/features/browser_ui/6_release/deploy_key/clone_using_deploy_key_spec.rb Quality, ~"S1", ~"bug", ~"devops::release", found:nightly
• - #36258 (closed) Get protected environment details via API api, customer, ~"devops::release", environments, feature
• - #36257 (closed) Release edit button is visible even if the user doesn't have permission to edit the release ~"S2", ~"bug", ~"devops::release", ~"group::release management"
• - #36210 (closed) Write feature spec for environment dashboard ~"devops::release", ~"technical debt"
• - #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"
• - #35741 Add UI support for displaying merge requests deployed in a deployment - Merge Request View ~"Accepting merge requests", Deliverable, Delivery, UX, deploy, ~"devops::release", direction, feature, frontend, ~"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 ~"Accepting merge requests", Enterprise Edition, GitLab Premium, ~"ReleaseP1", ~"ReleaseP2", ~"devops::release", direction, feature, ~"group::progressive delivery", workflowblocked
• - #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