Updates to the Bug Prioritatization report to include new conditions

What does this MR do and why?

Describe in detail what your merge request does and why.

Based on the Feedback from the product teams on Automated Bug Prioritatization report, the following changes have been implemented:

• If a bug already has the current milestone assigned, then we can exclude it as its been looked upon (also if its assigned to someone)
• Include SLOMissed and SLONear Miss labelled issues
• Displaying the Upvotes on the issues to determine the impact of fixing an issue
• There are few issues marked with workflowblocked labels, which we might want to ignore from the report because it requires either a larger investment to resolve them, or they are dependent on another issue, potentially owned by another team
• Since bugvulnerability is mostly looked into immediately, we should be excluding it in our report or add it as last section after showing the top level bugs

Expected impact & dry-runs

• Performed dry-run for multiple groups (code review, source code, authentication etc) and ensured that the report was generated correctly

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