Convert issue templates to issue forms (#1158)

* Convert bug report template to issue form

* Convert feature request template to issue form

* Convert documentation request template to issue form

* refactor(feature-request): rename textarea to Feature Description

* refactor(documentation-request): rename textarea to Documentation Description

Author: FrozenSoda

.github/ISSUE_TEMPLATE/bug-report.md

@@ -0,0 +1,69 @@
+name: Bug Report
+description: Bugs in AMP, the instance manager, or official AMP modules.
+labels: [bug]
+body:
+- type: markdown
+  attributes:
+    value: |
+      Please only include one issue per post! Do not try and bring up multiple requests in a single post.
+- type: input
+  attributes:
+    label: Operating System
+    description: Include distribution name and version number.
+    placeholder: Debian 12.6.0
+  validations:
+    required: true
+- type: input      
+  attributes:
+    label: AMP Version and Build Date
+    description: |
+      Always use the version number, 'latest' is not valid!
+    placeholder: 2.5.1.6 - 20240816.1
+  validations:
+    required: true
+- type: dropdown      
+  attributes:
+    label: AMP Release Stream
+    options:
+      - LTS
+      - Mainline
+      - Preview
+      - Development
+  validations:
+    required: true
+- type: checkboxes
+  attributes:
+    label: I confirm that
+    options:
+      - label: I have searched for an existing bug report for this issue.
+        required: true
+      - label: I am using the latest available version of AMP.
+        required: true
+      - label: my operating system is up-to-date.
+        required: true
+- type: textarea
+  attributes:
+    label: Intended Action
+    description: What are you trying to do?
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Expected Behaviour
+    description: What are you expecting to happen?
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Actual Behaviour
+    description: |
+      What is actually happening? 'Nothing' is not an acceptable answer!
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Reproduction
+    description: |
+      Starting from a clean install, how do you reproduce the issue that causes the symptoms described above? Imagine you're describing the problem to someone who has no idea what AMP is and needs to recreate the issue themselves.
+  validations:
+    required: true

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -0,0 +1,18 @@
+name: Documentation Request
+description: To request documentation on a given aspect of AMP.
+labels: [documentation]
+body:
+- type: markdown
+  attributes:
+    value: |
+      Please include the following:
+      * Links to any existing documentation if it exists but is unclear.
+      * Information on what feature/aspect of AMP needs documenting.
+      * What you're currently trying to do with AMP that has led you to require the given feature.
+      * Some background on what information you might like to see in the documentation.
+- type: textarea
+  attributes:
+    label: Documentation Description
+    description: Describe your request.
+  validations:
+    required: true

.github/ISSUE_TEMPLATE/documentation-request.md

@@ -0,0 +1,20 @@
+name: Feature Request
+description: To request new features for either AMP or one of its application modules.
+labels: [enhancement]
+body:
+- type: markdown
+  attributes:
+    value: |
+      Note that this is not for requesting support for new games/applications. To do this you should go to https://github.com/CubeCoders/AMPTemplates and first attempt to build a configuration yourself - otherwise you can request a template from that repo.
+- type: checkboxes
+  attributes:
+    label: I confirm that
+    options:
+      - label: I have searched for an existing feature request matching the description.
+        required: true
+- type: textarea
+  attributes:
+    label: Feature Description
+    description: Describe your request.
+  validations:
+    required: true