Issue template overhaul

[moritztim]

Bug Report

• Use <details>
• Add checkboxes (except to "Other Notes")
• Add <pre> to command output fields

(markdown formatting doesn't work one line below or above any html tag so I used <pre> to make it more compact)

• Separate titles and instructions

Some of the titles included instructions in them, some of them in <!---> comments, now all instructions are in comments.

• fix typo in title
• Separate titles from each other, so the user can see the structure at a glance
• Shorten title
• Use headings

Feature Request

• Make titles declarative instead of imperative
• Change title to align with bug report
• Use headings

[moritztim]

Look at it first, maybe you don't want checkboxes cause github sees them as task lists

[moritztim]

[jmmaranan]

Yes, it should be as simple and less friction as possible. I think checkboxes are for a PR not the issue nor feat templates. Correct that and I think everything else looks fine.

[moritztim]

The advantage of not having checkboxes is you could turn the sections into headings, should I do that? With ## or ### whatever looks good.
That instead of ** ** would make it more readable and less cluttered in the editor

[moritztim]

I used ## headings.
Try it:
https://github.com/moritz-t-w/forge/issues/new

[moritztim]

Now we have cool forms :D

[moritztim]

@jmmaranan please do take a look at the forms: https://github.com/moritz-t-w/forge/tree/main/.github/ISSUE_TEMPLATE to see if you agree which fields should be required