Automatically apply ~"analytics instrumentation" label

What does this MR do and why?

Relates to issue: Automatically apply ~"analytics instrumentation... (gitlab-org/gitlab#465686) • Tanuja Jayarama Raju

Automatically apply ~"analytics instrumentation" label when featureaddition and workflowready for development labels are applied

Why?

• it serves as a reminder to teams to add instrumentation. Teams can remove the label when instrumentation for whatever reason doesn't apply to the feature
• It helps the groupanalytics instrumentation to track features that need instrumentation and pro-actively reach out to teams to provide support and address pain 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