Move active global search issues and MRs to the current milestone

What does this MR do and why?

Moves any open groupglobal search issue or merge request with either workflowin dev or workflowin review to the current milestone if they are already not assigned current or future milestone.

Expected impact & dry-runs

Dry run: https://gitlab.com/gitlab-org/quality/triage-ops/-/jobs/8339920739

• Example issue that should be put into current milestone: gitlab-org/gitlab#463374
• Example MR that should be put into current milestone: gitlab-org/gitlab!161781
• Example MR that would be skipped (because it has a milestone assigned): gitlab-org/gitlab!165729

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