Remove Compliance group from missed resource flow

What does this MR do and why?

Describe in detail what your merge request does and why.

Only add ~missed::xy label for Compliance group issues when have ~goal::complete label present. Remove all ~goal:: scoped labels from issues at end of milestone.

The reason for making this change is that in the Compliance group we recently introduced ~goal:: scoped labels to our issues to clearly indicate expectation during a milestone, gitlab-com/www-gitlab-com!128671 (diffs). Some issue will be assigned and certain things expected in a milestone (planning or begun development or simply a stretch to even get to it), but not expected to actual close.

One of the reason for this change was the missed labels that were automatically added to issue at end of a milestone was causing anxiety in engineers that they were not meeting expectations, a big red missed label added to their assigned issues. We wanted to remove this anxiety and only focus on the ~goal::complete and ~deliverable labelled issues as major talking points.

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