Add people selection group and reviewer filter to auto-triage

[potiuk]

Summary

• Group --author, --include-collaborators, --reviews-for-me, --reviews-for into a dedicated
  "Select people" section in the breeze pr auto-triage help output
• Rename --review-requested to --reviews-for-me for clarity
• Add --reviews-for option (mutually exclusive with --reviews-for-me) to filter PRs by specific
  reviewer(s), with shell autocomplete from a locally cached collaborators list that is
  refreshed in the background on each command invocation
• Add HiddenChoiceWithCompletion param type that provides tab-completion without listing
  choices in --help
• Simplify triage comments posted on collaborator-authored PRs: no emojis, no instruction
  links, no "What to do next" — just the issues

Test plan

• Run breeze pr auto-triage --help and verify "Select people" group appears with all four options
• Run breeze pr auto-triage --reviews-for-me --reviews-for someone and verify mutual exclusion error
• Run breeze pr auto-triage --reviews-for user1 --reviews-for user2 --dry-run and verify multi-reviewer fetch
• Run breeze pr auto-triage --reviews-for-me --dry-run and verify it filters by authenticated user
• Verify collaborator cache is created in .build/ after a run
• Verify --reviews-for tab-completion works after cache is populated

---

Was generative AI tooling used to co-author this PR?

• Yes — Claude Opus 4.6

Generated-by: Claude Opus 4.6 following the guidelines

[potiuk]

Next iteration of auto-triage

[choo121600]

Wow 🙌

[choo121600]

Small question: “--my-reviews” might be interpreted as reviews that I have written. I actually had the same concern when implementing this feature.

That said, I can’t think of a better alternative right now, so I think the current wording is probably fine.

[potiuk]

That said, I can’t think of a better alternative right now, so I think the current wording is probably fine.

Yeah. Naming is hard. --reviews-for-me maybe ?

[potiuk]

And --reviews-for for others.

[choo121600]

Yeah, --reviews-for-me and --reviews-for sound much clearer to me 👍

[github-actions]

Backport failed to create: v3-1-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-1-test

You can attempt to backport this manually by running:

cherry_picker 4b69954 v3-1-test

This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.