Add Remote Development Workflow Ignore

What does this MR do and why?

A small MVC to follow-up on gitlab-org/gitlab#397005 (comment 1503758511):

We might even want to introduce a new generic ~rd-workflow::ignore state to be used for this purpose, which would allow us to write the automation rules in a generic way. And we could also even show this column on the iteration board if we wanted to have visibility of them there, but outside the standard process flow.

• https://gitlab.com/groups/gitlab-org/-/labels?subscribed=&search=rd-workflow

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