Regenerate policies to move respond to service management

What does this MR do and why?

With Regenerate policies to move respond to monitor (!2537 - merged) we moved the respond group to the monitor stage, but that's not what we want in the long run. The respond group and the associated categories are not owned by the Monitor stage. The Respond group is now owned by the Service Desk Single-Engineer-Group and therefore has been moved to the SEG's section in Moves Respond group under the new Service Desk ... (gitlab-com/www-gitlab-com!131590 - merged) Instead of creating a new devops::service-desk stage we use the sevops::service-management because the respond group owns all Service Management categories within GitLab.

This MR updates the policy file for the respond group to add the correct devops::service.management label.

Expected impact & dry-runs

These are strongly recommended to assist reviewers and reduce the time to merge your change.

See https://gitlab.com/gitlab-org/quality/triage-ops/-/tree/master/doc/scheduled#testing-policies-with-a-dry-run on how to perform dry-runs for new policies.

See https://gitlab.com/gitlab-org/quality/triage-ops/-/blob/master/doc/reactive/best_practices.md#use-the-sandbox-to-test-new-processors on how to make sure a new processor can be tested.

Action items

• If adding environment variables for reactive processors, update config/triage-web.yaml and .gitlab/ci/triage-web.yml
• (If applicable) Add documentation to the handbook pages for Triage Operations =>
• (If applicable) Identify the affected groups and how to communicate to them:
  • /cc @person_or_group =>
  • Relevant Slack channels =>
  • Engineering week-in-review