Update the bug templates to include type, convert Feature to yaml (#18018)

.github/ISSUE_TEMPLATE/Bug_Report.yml

@@ -1,6 +1,7 @@
 name: "Bug report 🐛"
 description: Report errors or unexpected behavior
 labels: [Issue-Bug, Needs-Triage]
+type: Bug
 body:
 - type: markdown
   attributes:
@@ -12,7 +13,7 @@ body:
 - type: input
   attributes:
     label: Windows Terminal version
-    placeholder: "1.7.3651.0"
+    placeholder: "1.21.2701.0"
     description: |
       You can copy the version number from the About dialog. Open the About dialog by opening the menu with the "V" button (to the right of the "+" button that opens a new tab) and choosing About from the end of the list.
   validations:
@@ -21,7 +22,7 @@ body:
 - type: input
   attributes:
     label: Windows build number
-    placeholder: "10.0.19042.0"
+    placeholder: "10.0.22621.0"
     description: |
       Please run `ver` or `[Environment]::OSVersion`.
   validations:
@@ -32,9 +33,9 @@ body:
     label: Other Software
     description: If you're reporting a bug about our interaction with other software, what software? What versions?
     placeholder: |
-      vim 8.2 (inside WSL)
-      OpenSSH_for_Windows_8.1p1
-      My Cool Application v0.3 (include a code snippet if it would help!)
+      vim 9.1 (inside WSL)
+      OpenSSH_for_Windows_9.5p1
+      My Cool Application v0.4 (include a code snippet if it would help!)
   validations:
     required: false
 

.github/ISSUE_TEMPLATE/Documentation_Issue.md

@@ -1,10 +0,0 @@
----
-name: "Documentation Issue 📚"
-about: Report issues in our documentation
-title: ''
-labels: Issue-Docs
-assignees: ''
-
----
-
-<!-- Briefly describe which document needs to be corrected and why. -->

.github/ISSUE_TEMPLATE/Feature_Request.md

@@ -1,35 +0,0 @@
----
-name: "Feature Request/Idea 🚀"
-about: Suggest a new feature or improvement (this does not mean you have to implement
-  it)
-title: ''
-labels: Issue-Feature
-assignees: ''
-
----
-
-<!-- 
-🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨
-
-I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
-1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
-2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
-3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
-4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
-5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.
-
-All good? Then proceed!
--->
-
-# Description of the new feature/enhancement
-
-<!-- 
-A clear and concise description of what the problem is that the new feature would solve.
-Describe why and how a user would use this new functionality (if applicable).
--->
-
-# Proposed technical implementation details (optional)
-
-<!-- 
-A clear and concise description of what you want to happen.
--->

.github/ISSUE_TEMPLATE/Feature_Request.yml

@@ -0,0 +1,20 @@
+name: "Feature Request/Idea 🚀"
+description: Suggest a new feature or improvement (this does not mean you have to implement it)
+labels: [Issue-Feature]
+type: Feature
+body:
+- type: textarea
+  attributes:
+    label: Description of the new feature
+    description: A clear and concise description of what the problem is that the new feature would solve.
+    placeholder: |
+      ... and guess what? I have four Terminals. And I have a hover car, and a hover house. And my computer's a runner, and it shows.
+  validations:
+    required: true
+
+- type: textarea
+  attributes:
+    label: Proposed technical implementation details
+    description: This field is optional. If you have any ideas, let us know!
+  validations:
+    required: false