Consider adding automation

[z-a-f]

If this project to survive, there is a number of ways to reduce the repo management pressure (aside from adding more maintainers). Below are some suggestions that will drastically improve the work-life balance lolol

1. Issue forms and PR templates will prevent bad work from entering the queue
2. actions/labeler will automatically tag PRs by changed paths. This will allow faster filtering for reviewers
3. CODEOWNERS will allow auto-request for exact people
4. Branh protection / rules will let you avoid "babysitting" the merges
5. Merge queue will save time by avoiding "red after merge"
6. actions/stale and lee-dohm/no-response will help with maintainers' backlog entropy. Careful with this one -- if not configured correctly, community might get upset :)
7. Dependabot and Code scanning to help detect unsafe PRs

In addition to the ones above, there are some other tools that help, but IMHO need strict rules for maintainers:

1. AI code review -- use this as a first-pass reviewer, not a gatekeeper.
2. Auto issue resolver -- these only work in very specific use-cases. IMHO:
   • [OK] Rerouting issues to discussions / FAQ / docs etc.
   • [OK] Auto-labeling + templating
   • [OK] Sorting duplicates
   • [OK] Marking for stale or needs-info for incomplete reports
   • [NOT OK] Aggressive duplicate-closing bots
   • [NOT OK] "AI issue solver" that auto-closes on bug reports
   • [NOT OK] Authoritative auto-responders -- most of them make shit up

cc @rohitprasad15 @andrewyng