Migrates Issue Reporting to the New GitHub Template Format

[san7890]

About The Pull Request

Screenshots slightly outdated, check it out here for the latest: https://github.com/san7890/bruhstation/blob/issue-reporting/.github/ISSUE_TEMPLATE/bug_report_form.yml

Gone are the days of copypasting markdowns and people leaving out important information! A much cleaner form is upon us!

First off, the button will now automatically redirect people to the forums for feature requests. No more accidental entries through blank MDs, should be a lot cleaner.

If it is a valid issue report, you'll be navigated to this menu. No more having to worry about putting comments in the input field as the important information is fully visible in the form:

Template Image

This will be the end result of filling in all the fields:

End Result

### Client Version

515.1642

### Issue Summary

insert blank here

### Round ID

_No response_

### Test Merges

perhaps

### Reproduction steps

alirght

I updated the BYOND-side code to ensure that this would work just as it did prior, auto-filling the applicable fields that we generate ingame.

Why It's Good For The Game

Far more clarity to people who wish to report issues, no more worrying about comment formatting, can have mandatory fields, just a cleaner experience overall.

Changelog

🆑
qol: Reporting issues on the Github should now be a far more simpler experience. Hitting the "Report Issue" button in the top-right of your BYOND Client Screen will still autofill in the fields as expected.
/:cl:

Ignore how dumb the commit history of this branch is.

[san7890]

@tgstation/commit-access FYI: Updating how issue reports work. Should be a far cleaner experience, please let me know if some fields should be mandatory or not, I used my judgement in selecting which ones should be required.

[MrMelbert]

Out of curiosity have you tested the in game report issue button?

It currently fills out a bunch of information for the user (version, round id, test merges) which is very handy and it would kinda suck to lose that

[MrMelbert]

Oh I see you actually changed the code involving that nvm, it still auto-fills in I assume?

[LemonInTheDark]

This is really cool, major improvement

[san7890]

Oh I see you actually changed the code involving that nvm, it still auto-fills in I assume?

yea here's a small example, https://github.com/san7890/bruhstation/issues/new?assignees=&labels=&projects=&template=bug_report_form.yml&issue-summary=big. notice how the word "big" is autofilled in the field, since issue-summary pairs 1:1 with the id field we set for that segment in the YML. really nice thing from github that made this 100x easy, the code worked as expected on my local machine for stuff like the round ID and what not.

[san7890]

@MrStonedOne forgot to FYI you on this too

[san7890]

line of concern removed, now this button is available. let me know if you have something else in mind