Add quarantined::broken section to the group reports

What does this MR do and why?

Add quarantined::broken section to the group reports

Expected impact & dry-runs

https://gitlab.com/gitlab-org/quality/triage-ops/-/jobs/6344888277

#### Open quarantined broken specs issues
- [ ] gitlab-org/gitlab#446114 Failures in spec/models/preloaders/user_max_access_level_in_projects_preloader_spec.rb:38 and 45 and 56 ~"Category:System Access", ~"devops::govern", ~"group::authentication", ~"quarantine", ~"quarantine::broken", ~"section::sec"
- [ ] gitlab-org/gitlab#446111 Failures in spec/helpers/users_helper_spec.rb:630 ~"Category:User Management", ~"devops::govern", ~"group::authentication", ~"quarantine", ~"quarantine::broken", ~"section::sec"
- [ ] gitlab-org/gitlab#444713 Failures in spec/helpers/users_helper_spec.rb:616 ~"Category:User Management", ~"devops::govern", ~"group::authentication", ~"quarantine", ~"quarantine::broken", ~"section::sec"
- [ ] gitlab-org/gitlab#444712 Failures in spec/models/preloaders/user_max_access_level_in_projects_preloader_spec.rb:22 ~"Category:System Access", ~"devops::govern", ~"group::authentication", ~"quarantine", ~"quarantine::broken", ~"section::sec"

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

Closes #1495 (closed)