Add WIP check to automated review request for UX MRs

What does this MR do and why?

We found that some community contribution MRs receive the UX label only after it's further down in the workflow than when the workflowready for review label is applied. See example case for reference. @mvanremmerden suggested removing the workflowready for review label check to avoid missing notifications for UX MRs that proceed to merge without a review request.

This MR removes the workflowready for review check and instead checks whether MRs are NOT in WIP or draft status for the automated review request UX processor.

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-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