Issue template labels and consistency

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,5 +1,5 @@
 ---
-name: 🐛 Bug report
+name: 🐛 Bug Report
 about: Create a report to help us improve
 title: ''
 labels: 'bug,triage'

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,5 +1,5 @@
 ---
-name: 🙋 Feature request
+name: 🙋 Feature Request
 about: Suggest an idea for this project
 title: ''
 labels: 'enhancement,triage'
@@ -11,6 +11,8 @@ Thanks for filing an issue 😄! Before you submit, please read the following:
 Search open/closed issues before submitting. Someone may have requested the same feature before.
 -->
 
+# 🙋 Feature Request
+
 ## 😯 Problem to Solve
 
 <!--- Provide a clear and concise description of why this feature is wanted or what problem it solves. -->

.github/ISSUE_TEMPLATE/ixd_user_story.md → .github/ISSUE_TEMPLATE/interaction_design_request.md

@@ -1,12 +1,14 @@
 ---
-name: 🧑‍💼 Interaction Design (IxD) User story
+name:  👈 Interaction Design Request
 about: (PO ONLY) A small chunk of work to be done by an Interaction Designer
 title: 'nimble-{name} interaction design request'
-labels: 'IxD,triage'
+labels: 'interaction design,triage'
 ---
 
 <!-- Ensure the title can be understood without the parent item's context, e.g. "nimble-datepicker interaction design request" rather than just "Interaction Design" -->
 
+# 👈 Interaction Design Request
+
 ## 📌 Request Background
 
 <!-- A short description of the request and requester. E.g. Who is the client and how do they expect to use the component? -->
@@ -33,4 +35,4 @@ labels: 'IxD,triage'
 
 - [ ] Interaction Design Spec submitted (link)
 - [ ] Interaction Design Spec reviewed by design team
-- [ ] Interaction Design Spec reviewed by dev team
+- [ ] Interaction Design Spec reviewed by dev team

.github/ISSUE_TEMPLATE/new_component.md

@@ -1,10 +1,12 @@
 ---
-name: 💡 New component
+name: 💡 New Component
 about: (DEV TEAM ONLY) New Nimble component
 title: 'nimble-{name} Component'
-labels: 'enhancement'
+labels: 'new component,enhancement'
 ---
 
+# 💡 New Component
+
 ## 😯 Problem to Solve
 
 <!-- List any clients/contacts that specifically need this component, or note that the component just adds general utility. -->
@@ -18,8 +20,7 @@ labels: 'enhancement'
 
 ## 📋 Tasks
 
-<!-- Refer to [CONTR
-IBUTING](https://github.com/ni/nimble/blob/main/packages/nimble-components/CONTRIBUTING.md) for details -->
+<!-- Refer to https://github.com/ni/nimble/blob/main/packages/nimble-components/CONTRIBUTING.md for details -->
 
 - [ ] nimble-{name} interaction design issue
 - [ ] nimble-{name} interaction design spec

.github/ISSUE_TEMPLATE/tech_debt.md

@@ -1,7 +1,8 @@
 ---
-name: 🧹 Tech debt
+name: 🧹 Tech Debt
 about: (DEV TEAM ONLY) Non-user-visible improvement to code or development process
 title: ''
 labels: 'tech debt,triage'
 ---
-## 🧹 Tech Debt
+
+# 🧹 Tech Debt

.github/ISSUE_TEMPLATE/user_story.md

@@ -6,4 +6,4 @@ title: '(Fully descriptive title)'
 
 <!-- Ensure the title can be understood without the parent item's context, e.g. "nimble-button Angular wrapper" rather than just "Angular wrapper" -->
 
-## 📌 User Story
+# 📌 User Story

.github/ISSUE_TEMPLATE/visual_design_user_story.md → .github/ISSUE_TEMPLATE/visual_design_request.md

@@ -1,12 +1,14 @@
 ---
-name: 🧑‍🎨 Visual Design (ViD) User story
+name: 🎨 Visual Design Request
 about: (DEV TEAM ONLY) A small chunk of work to be done by Visual Designer
 title: 'nimble-{name} visual design request'
-labels: 'ViD,triage'
+labels: 'visual design,triage'
 ---
 
 <!-- Ensure the title can be understood without the parent item's context, e.g. "nimble-datepicker Visual Design" rather than just "Visual Design" -->
 
+# 🎨 Visual Design Request
+
 ## 📌 Request Background
 
 <!-- A short description of the request and requester. E.g. Who is the client and how do they expect to use the component? -->
@@ -33,4 +35,4 @@ labels: 'ViD,triage'
 
 - [ ] Visual Design Spec submitted (link)
 - [ ] Visual Design Spec reviewed by design team
-- [ ] Visual Design Spec reviewed by dev team
+- [ ] Visual Design Spec reviewed by dev team