Suggestion: Add "required label" bot to assist with triage

Challenge: Ensuring things are triaged and filed appropriately.

Goal: Make this easier and visible without being obstrusive

Suggestion: utilize an instance of the probot-require-label bot.

How to set up:

• Fork the probot-require-label repo (we don't have to do this; we can technically reference it directly if we want)
• Deploy (Glitch is a great free way to do this)
• Create a GitHub app and add the private key to the glitch app we've deployed
• Add a webhook to the bot app on glitch so that it receives the events

How it works:

• We create a configuragtion file
• When a type of label is missing, it applies a label of our choice

Suggested configurations:

• Apply a needs:triage when the triaged label is not applied
• Apply a needs:type when a type label is not applied
• Apply a needs:priority when a priority label is not applied
• Apply a needs:area when an area label is not applied

Start by reviewing the proposed probot-require-label setup and the repository's current label workflow. Check the Glitch deployment, GitHub App private key, webhook, and configuration steps described in the issue. Done means the bot applies the intended needs:triage, needs:type, needs:priority, and needs:area labels when their corresponding labels are missing.