Replace issue templates with forms

Squashed commit of the following:

commit 2ff95cf
Author: retke <laggron42@gmail.com>
Date:   Wed Dec 29 12:48:29 2021 +0100

    Github wants unique names

commit f9d07a4
Author: retke <laggron42@gmail.com>
Date:   Wed Dec 29 12:44:55 2021 +0100

    Add issue templates

.github/ISSUE_TEMPLATE/01_bug_report.yml

@@ -0,0 +1,76 @@
+name: Bug Report
+description: Report a bug with a cog.
+labels: ["Type: Bug", "Status: Pending"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report!
+        If you need help with using the cogs instead, please join the [support server](https://discord.gg/GET4DVk).
+  - type: input
+    id: red-version
+    attributes:
+      label: Red's version
+      description: |
+        What is the version of Red you're using?
+        Use `[p]info` or `redbot --debuginfo` to see this.
+      placeholder: 3.5.0
+    validations:
+      required: true
+  - type: dropdown
+    id: cog-name
+    attributes:
+      label: The cog you're using.
+      description: If the problem is global to the repo (like logging), leave this blank
+      options:
+        - CodMW
+        - InstantCommands
+        - RoleInvite
+        - Say
+        - Tournaments
+  - type: input
+    id: cog-version
+    attributes:
+      label: The cog's version
+      description: |
+        What is the version of the cog? This is required if the problem isn't global.
+        To get the version of your cog, use the `[p]<cogname>info` command. (ex: `[p]sayinfo`, `[p]warnsysteminfo`, `[p]tournamentsinfo`...)
+      placeholder: 1.4.0
+  - type: input
+    id: command
+    attributes:
+      label: The command you're using
+      description: If this isn't bounded to a specific command, leave this blank
+      placeholder: "warn"
+  - type: textarea
+    id: expectations
+    attributes:
+      label: "What did you expect to happen?"
+    validations:
+      required: true
+  - type: textarea
+    id: result
+    attributes:
+      label: "What actually happened?"
+      description: |
+        A clear and concise description of what the bug is.
+        If the issue is visual in nature, consider posting a screenshot.
+    validations:
+      required: true
+  - type: textarea
+    id: reproduction-steps
+    attributes:
+      label: "How can we reproduce this error?"
+      description: "List of steps required to reproduce this error."
+      value: |
+        1.
+        2.
+        3.
+        ...
+    validations:
+      required: true
+  - type: textarea
+    id: anything-else
+    attributes:
+      label: Anything else?
+      description: Let us know if you have anything else to share.

.github/ISSUE_TEMPLATE/02_feature_request.yml

@@ -0,0 +1,62 @@
+name: Feature Request
+description: For feature requests.
+labels: ["Status: Pending", "Type: Suggestion"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for taking the time to fill out an issue, this template is meant for any feature suggestions.
+        If you need help with using the cogs instead, please join the [support server](https://discord.gg/GET4DVk).
+  - type: dropdown
+    id: feature-name
+    attributes:
+      label: "Type of feature request"
+      description: "What type of feature would you like to request?"
+      multiple: true
+      options:
+        - API functionality
+        - Cog
+        - Command
+        - Other
+    validations:
+      required: true
+  - type: dropdown
+    id: cog-name
+    attributes:
+      label: The cog your feature request is for.
+      description: If the suggestion is global to the repo (like a new cog), leave this blank
+      options:
+        - CodMW
+        - InstantCommands
+        - RoleInvite
+        - Say
+        - Tournaments
+  - type: textarea
+    id: proposal
+    attributes:
+      label: "Description of the feature you're suggesting"
+      description: |
+        Feel free to describe in as much detail as you wish.
+
+        If you are requesting a command:
+          - Include what cog it should be in and a name for the command
+          - Describe the intended functionality for the command
+          - Note any restrictions on who can use the command or where it can be used
+
+        If you are requesting API functionality:
+          - Describe what it should do
+          - Note whether it is to extend existing functionality or introduce new functionality
+
+        If you are requesting a new cog: 
+          - Describe the functionality in as much detail as possible
+          - Include the command structure, if possible
+          - Please note that there are few chances I actually make new cogs
+            based on suggestions (but could always happen).
+          - If you're asking for a commission, DM me (El Laggron) or use the [cogboard](https://cogboard.discord.red/)
+    validations:
+      required: true
+  - type: textarea
+    id: anything-else
+    attributes:
+      label: Anything else?
+      description: Let us know if you have anything else to share.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: true
+contact_links:
+  - name: 3rd party cog support server
+    url: https://discord.gg/GET4DVk
+    about: The Discord server for support with 3rd party cogs. Head to the \#support_laggrons-dumb-cogs channel