Create initial designs for a Github Triage Bot

[aubrey-oneal]

While we have a triaging workflow for feature requests in addition to labeling (i.e. 'community contribution' and the Enhancement Project Board), our contributors don't get a clear look into the triage process. The goal of this issue is to utilize a triage bot to increase transparency into our process within Github issues, automate wherever possible, and find a better way to kick off community contribution work.

• Create plan for a triage bot with the ability to comment based on label triggers #14294
• Add issue labels needed for triggers ('design contribution needed' and 'developer contribution needed')
• Review VSCodeTriageBot by Microsoft VSCode for inspiration:
• Feature request backlog/process expectation setting
• Bug reports needing more info, or a reproduction
• Issues not in english
• Pointing out bugs may be fixed in the latest version

[aubrey-oneal]

Rough draft of a bot workflow

[aubrey-oneal]

Info provided by Taylor:
We'll need to make a workflow to house the logic for when and how to post the messages to issues.
There aren't triggers (yet?) for events that happen within the new github projects, like moving pipelines. The existing project trigger only works for classic projects 😞
We won't be able to use hramos/label-actions@v1 but we should be able to get the same result using if expressions on different jobs or steps in the workflow and use actions/github-script@v6 to add the comment