chore: update issue templates

Add `type: Bug` to bug_report.md and `type: Feature` to issue-template.md, and convert the visible guidance text into HTML comments so placeholder instructions don't render in the created issue.

Signed-off-by: Alex Piatakov <alex.piatakov@swirldslabs.com>

Author: Pyatakov

.github/ISSUE_TEMPLATE/bug_report.md

@@ -4,21 +4,23 @@ about: Create a report to help us improve
 title: ''
 labels: ''
 assignees: ''
+type: Bug
 
 ---
 
 ### Problem description
-A clear and concise description of what the bug is.
+<!-- A clear and concise description of what the bug is.  -->
 
 ### Step to reproduce
-Steps to reproduce the behavior:
+<!-- Steps to reproduce the behavior:
 1. Go to '...'
 2. Click on '....'
 3. Scroll down to '....'
 4. See error
+-->
 
 ### Expected behavior
-A clear and concise description of what you expected to happen.
+<!-- A clear and concise description of what you expected to happen.  -->
 
 ### Screenshots
-If applicable, add screenshots to help explain your problem.
+<!-- If applicable, add screenshots to help explain your problem.  -->

.github/ISSUE_TEMPLATE/issue-template.md

@@ -4,17 +4,18 @@ about: To record product requirements in the form ready for developers to pick u
 title: ''
 labels: ''
 assignees: ''
+type: Feature
 
 ---
 
 ### Problem description
-Describe the current state of affairs and why it needs to change.
+<!-- Describe the current state of affairs and why it needs to change.  -->
 
 ### Requirements
-Exact requirement for the product - what needs to be done?
+<!-- Exact requirement for the product - what needs to be done?  -->
 
 ### Definition of done
-How do we know we've fully dealt with it?
+<!-- How do we know we've fully dealt with it?  -->
 
 ### Acceptance criteria
-What are the criteria by which we determine if the issue has been resolved?
+<!-- What are the criteria by which we determine if the issue has been resolved?  -->