Next iteration growth team refinement automation

What does this MR do and why?

Related to: gitlab-org/growth/team-tasks#679 (closed)

1. Add a processor to add refinement thread when issue is moved into refinement
2. Add check in lib/growth_refine_automation_helper.rb to allow reacting with ❌ to block refinement

Expected impact & dry-runs

Dry run for scheduled: https://gitlab.com/gitlab-org/quality/triage-ops/-/jobs/3951543792

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