Print the actionable retry commands directly in master broken reports

What does this MR do and why?

• Incentivize to use the retry_pipeline command by default as it automatically retry all failed jobs anyway.
• Include the actual pipeline ID in the command so that people can just copy/paste & post.
• Print the individual retry_job command for each failed job, in any case.

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