Add issue forms for bugs

[victor-gp]

GitHub documentation for issue forms.

This is a great example for what should be included in a "Bug" issue.

Requirements:

1. command where the bug happens
2. description of the bug, left to the reporter's discretion. Ideally, one of:
   • screenshot of the bug
   • line in the help message where the bug appears, plus its pattern (e.g.: "arg1:arg2 arguments")
3. full help message
4. version number for the command where the bug happens

For easier copypasting, help message & version number should be 2 separate input fields.

[victor-gp]

Here's an example of how issue forms work on the Homebrew repo:

• source code
• issue form
• submitted issue

[victor-gp]

Nice-to-haves:

• automatically label the issue as bug
• construct the bug title like this from 2 input fields:
  • unhandled pattern
  • command where it happens
• ask the user to download the latest version of the syntax and try to reproduce the bug
  • we lack scripts for this: download, bat build cache and, more importantly: teardown
  • low priority

This would be a "Bug" template, but there should be an "Other" template that lets people report whatever, without constraints. I can probably handle that by enabling blank issues.

DoD for this issue, first iteration:

• just an issue form for bugs
• with fields for the aforementioned 4 requirements (though command + bug description may go together)
• The nice-to-haves are super optional (I don't even know if they're technically feasible), leave them for later

[victor-gp]

Closing this after the last few commits.