Proposal: Add List of flaky issues to team summary

What does this MR do and why?

Describe in detail what your merge request does and why.

Related with note gitlab-org/gitlab#398692 (comment 1325218657)

This is a proposal to add the flaky tests issue list to teams' summary reports.

This could be a simple boring solution to surface the flaky tests issues to teams.

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

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