Generate report script (urgent section)

[Crola1702]

Description

As discussed in #57 (comment), the new report must contain an urgent section.

The generate_report.rb uses the library from #60 to generate a JSON file containing information from all sections of the defined report. As an example:

{
  "urgent": {
    "build_regressions": [ ... ],
    "test_regressions_consecutive": [ ... ],
    "test_regressions_flaky": [ ... ]
  },
  "maintenance": {
    "jobs_failing": [ <empty> ],
    "gh_issues_reported": [ <empty> ],
    "tests_disabled": [ <empty> ]
  },
  "pending": {
    "build_regressions_known": [ <empty> ],
    "test_regressions_all": [ <empty> ],
    "test_regressions_known": [ <empty> ],
    "build_regressions_known": [ <empty> ]
  }
}

A complete example generated report: buildfarm-report_2024-06-25_12-10.json

[Crola1702]

@Blast545 #64 is what I've been working on for formatting.

Ideas about formatting of next sections include:

• Pretty titles: Some capitalization and spacing to make titles more readable
• Format as tables with internal lists and summaries: There are really long outputs, and these can make the report pretty much unreadable.
• Group test consistent regressions: Consistent test regressions can be grouped by job name and age, assuming that two regressions that are happening in the same job and have the same amount of consecutive failures are part of a same issue.
• Group flaky test regressions: Flaky test regressions can be grouped by similar flakiness amount, that is, if two regressions are happening in the same set of jobs, they might be the same issue (as they're flaky we can't assure it, but it's the most probable statement)