Exclude master:broken and master:foss-broken from ep triage report

What does this MR do and why?

Describe in detail what your merge request does and why.

closes #1224 (closed)

Exclude any master:broken and master:foss-broken incident issues as these issues usually get resolved on the same day and thus do not need to be reported in the weekly triage report.

For example: this report is listing all of the master broken incidents from the last week which are all resolved by the time the report is generated. It is not necessary for the report triager to check them again.

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.

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