Switching issues over to use forms instead of markdown

Author: tpill90

.github/ISSUE_TEMPLATE/1-bug_report.yaml

@@ -0,0 +1,51 @@
+name: 🐞 Bug Report
+description: Create a report to help us improve
+title: "<title>"
+labels: ["Bug"]
+body:
+  - type: textarea
+    attributes:
+      label: Describe the bug
+      description: A clear and detailed description of what the bug is.  Describe what steps you've taken to troubleshoot the issue.
+      placeholder: "..."
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Expected Behavior
+      description: Explain what your expected behavior of the app is.  What is the difference between what it is currently doing, and what you think it should be doing.
+      placeholder: "..."
+    validations:
+      required: true
+
+  - type: dropdown
+    attributes:
+      label: Platform
+      options:
+        - Linux
+        - Docker
+        - Unraid (Ich777's App)
+        - Windows
+        - Linux ARM
+        - MacOS
+    validations:
+      required: true
+
+  - type: input
+    attributes:
+      label: Discord Username
+      description: If you are part of the Lancache Discord Server this helps with communicating across both Github and Discord.
+    validations:
+      required: false
+
+  - type: textarea
+    attributes:
+      label: Anything else?
+      description: |
+        Screenshots? Logs? Anything that will give us more context about the issue you are encountering!
+
+        EpicPrefill's logs can be found in the application's directory alongside the executable.
+      placeholder: "..."
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/2-feature_request.yaml

@@ -0,0 +1,19 @@
+name: 💭 Feature Request
+description: Have an idea for new functionality?
+title: "[Feature Request]"
+labels: ["Feature Request"]
+body:
+  - type: textarea
+    attributes:
+      label: Description
+      description: Describe the new feature.  What is the new functionality?  What is the use case?  What is the user interface and how is it intended to be used?
+      placeholder: "..."
+    validations:
+      required: true
+
+  - type: input
+    attributes:
+      label: Discord Username
+      description: If you are part of the Lancache Discord Server this helps with communicating across both Github and Discord.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/3-question.yaml

@@ -0,0 +1,19 @@
+name: ❓ Question
+description: Need some clarification?  Looking for some guidance?  Ask away!
+title: "[Question]"
+labels: ["Question"]
+body:
+  - type: textarea
+    attributes:
+      label: Question
+      description: Ask away!
+      placeholder: "..."
+    validations:
+      required: true
+
+  - type: input
+    attributes:
+      label: Discord Username
+      description: If you are part of the Lancache Discord Server this helps with communicating across both Github and Discord.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/4-other.yaml

@@ -0,0 +1,17 @@
+name: Other
+description: For when the other issue types don't fit your issue.
+title: "<title>"
+body:
+  - type: textarea
+    attributes:
+      label: Description
+      placeholder: "..."
+    validations:
+      required: true
+
+  - type: input
+    attributes:
+      label: Discord Username
+      description: If you are part of the Lancache Discord Server this helps with communicating across both Github and Discord.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1 @@
+blank_issues_enabled: false

.github/ISSUE_TEMPLATE/config.yml

@@ -1,3 +1,4 @@
+# TODO Make sure there are no references to SteamPrefill in the various asciicasts
 site_name: epic-lancache-prefill wiki
 docs_dir: mkdocs
 repo_url: https://github.com/tpill90/epic-lancache-prefill