ci: Automatically create an incident for failing master pipelines

What does this MR do and why?

This MR ensures an incident is created in the gitlab-org/quality/engineering-productivity/master-broken-incidents project for each master pipeline failure.

The incident is then linked from the Slack #master-broken notification.

Example: https://gitlab.com/gitlab-org/gitlab/-/jobs/3220918271 created gitlab-org/quality/engineering-productivity/master-broken-incidents-playground#18 (closed)

Incident screenshot	Incident link in the Slack notification

Related to gitlab-org/monitor/respond#31 (closed) (resolve), https://gitlab.com/gitlab-org/quality/engineering-productivity/team/-/work_items/117062645 (resolve), https://gitlab.com/gitlab-org/quality/engineering-productivity/team/-/work_items/117062648 (resolve), #202195 (closed) (partially), gitlab-org/quality/triage-ops#816 (closed) (partially).

TODO before merge

• Change the value of BROKEN_MASTER_INCIDENTS_PROJECT_TOKEN with a Reporter/api project token for https://gitlab.com/gitlab-org/quality/engineering-productivity/master-broken-incidents/-/settings/access_tokens
• Change the value of BROKEN_MASTER_INCIDENTS_PROJECT to the final project

How to set up and validate locally

$ CI_PIPELINE_CREATED_AT="2022-10-23" scripts/create-pipeline-failure-incident.rb -p gitlab-org/quality/engineering-productivity/master-broken-incidents -t <project token>

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.