(AB#37680) Reorganize and rename issue templates

Prior to this change, distinguishing between issue templates and links
could be a little difficult.

This change:

- Reorders the issue templates so filing a bug is the first option, then
  suggesting an improvement, committing to a quality contribution, and
  finally reporting a product change
- Updates the issue template titles to use imperative language with a
  call to action and links in the issue picker to be questions
- Updates the Quality Contributions project links to point to the
  updated templates

Author: michaeltlombardi

.github/ISSUE_TEMPLATE/02-bug.yml renamed to .github/ISSUE_TEMPLATE/00-bug.yml

@@ -1,4 +1,4 @@
-name: "🐛 Report Documentation issue"
+name: "🐛 Report a documentation issue"
 description: >-
   Report an issue with current documentation.
 labels:

.github/ISSUE_TEMPLATE/01-article.yml

@@ -1,4 +1,4 @@
-name: "💡 New Document Request/Idea"
+name: "💡 Suggest a new document or idea"
 description: >-
   Suggest a new document or major rewrite of an existing one.
 labels:

.github/ISSUE_TEMPLATE/00-quality.yml renamed to .github/ISSUE_TEMPLATE/02-quality.yml

@@ -1,6 +1,6 @@
-name: "🛠️ Quality Contribution"
+name: "🦾 Commit to a Quality Contribution"
 description: >-
-  File a new issue to tackle quality improvement opportunities
+  File an issue to take part in the PowerShell Docs Quality Contributions project.
 title: "Quality: "
 body:
   - type: markdown

.github/ISSUE_TEMPLATE/config.yml

@@ -1,6 +1,6 @@
 blank_issues_enabled: true
 contact_links:
-  - name: Quality Contributions
+  - name: What's the Quality Contributions Project?
     url: https://learn.microsoft.com/powershell/scripting/community/contributing/quality-improvements
     about: >-
       If you'd like to commit to improving quality for the documentation, before filing an issue,