Improve monthly rp triage issues

What does this MR do and why?

Describe in detail what your merge request does and why.

The process around including bug and performance issues in the Release Post was changed. It no longer requires manually adding items to the RP MR but just links to an issue list.

Feedback was that we should keep the existing automation but update it as a reminder to add the correct labels and milestone so that the issues are included in this issue list.

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.

Related to Release Post 15.11 Retrospective (gitlab-com/www-gitlab-com#33872 - closed) where this came up.

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