Create a bug/triage checklist

This is an action item of the COE on hyper's surprise CVE:

There is a triage guide for bug reports, which is a good thing. But that doesn’t mean everyone (me included!) always remembers all the steps. Checklists are famous in aviation and medicine for their effectiveness in saving lives. They can also help us make sure all issues are treated properly.

Making sure the checklist is complete would be part of the routine decided on in #3214.

If I just take the headlines from the triager's guide, they would be this:

1. Acknowledge
2. Ask for more info
3. Categorize
4. Adjust the title
5. Mentor

I think there's a need to fill in a few more items for step 2, "Ask for more info".

There's also a question of how to make sure we complete the checklist for each bug report. One idea I had was to setup an autoresponder bot which includes the checklist in markdown checkbox form. Then the first comment would always have it, and triagers should have "edit" permissions which would be required to check them off.

Read the hyper triage guide linked in the issue and the routine proposed in #3214; compare the existing steps with the missing details for “Ask for more info.” Resolve whether the deliverable is a checklist, an autoresponder, or both, then define completion by a documented checklist that triagers can follow.