Don't create incident for draft MRs

What does this MR do and why?

gitlab-org/gitlab!210791 created two approved-mr-pipeline-incidents when in a draft state with no approvals, e.g. gitlab-org/quality/engineering-productivity/approved-mr-pipeline-incidents#9316

This MR ensures MRs in draft do not generates these incidents, rather than relying on the detailed_merge_status to be draft_status

Expected impact & dry-runs

These are strongly recommended to assist reviewers and reduce the time to merge your change.

See https://gitlab.com/gitlab-org/quality/triage-ops/-/tree/master/doc/scheduled#testing-policies-with-a-dry-run on how to perform dry-runs for new policies.

See https://gitlab.com/gitlab-org/quality/triage-ops/-/blob/master/doc/reactive/best_practices.md#use-the-sandbox-to-test-new-processors on how to make sure a new processor can be tested.

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