github: add issue templates for bug, enhancement, rfc, and feature req

Add issue templates from the Zephyr project for bug, enhancement, rfc, and
feature request issues.

Signed-off-by: Chris Friedt <[email protected]>

Author: Chris Friedt

.github/ISSUE_TEMPLATE/001_bug_report.md

@@ -0,0 +1,60 @@
+---
+name: Bug report
+about: Create a report to help us improve Tenstorrent Firmware
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+**Describe the bug**
+<!--
+A clear and concise description of what the bug is.
+
+Please also mention any information which could help others to understand
+the problem you're facing:
+ - What target platform are you using?
+ - What have you tried to diagnose or workaround this issue?
+ - Is this a regression? If yes, have you been able to "git bisect" it to a
+   specific commit?
+ - ...
+-->
+
+**To Reproduce**
+<!--
+Steps to reproduce the behavior:
+1. mkdir build; cd build
+2. cmake -DBOARD=board\_xyz
+3. make
+4. See error
+-->
+
+**Expected behavior**
+<!--
+A clear and concise description of what you expected to happen.
+-->
+
+**Impact**
+<!--
+What impact does this issue have on your progress (e.g., annoyance, showstopper)
+-->
+
+**Logs and console output**
+<!--
+If applicable, add console logs or other types of debug information
+e.g Wireshark capture or Logic analyzer capture (upload in zip archive).
+copy-and-paste text and put a code fence (\`\`\`) before and after, to help
+explain the issue. (if unable to obtain text log, add a screenshot)
+-->
+
+**Environment (please complete the following information):**
+
+ - OS: (e.g. Linux, MacOS, Windows)
+ - Toolchain (e.g Zephyr SDK, ...)
+ - Commit SHA or Version used
+
+**Additional context**
+<!--
+Add any other context that could be relevant to your issue, such as pin setting,
+target configuration, ...
+-->

.github/ISSUE_TEMPLATE/002_enhancement.md

@@ -0,0 +1,28 @@
+---
+name: Enhancement
+about: Suggest enhancements to existing features
+title: ''
+labels: Enhancement
+assignees: ''
+
+---
+
+**Is your enhancement proposal related to a problem? Please describe.**
+<!--
+A clear and concise description of what the problem is.
+-->
+
+**Describe the solution you'd like**
+<!--
+A clear and concise description of what you want to happen.
+-->
+
+**Describe alternatives you've considered**
+<!--
+A clear and concise description of any alternative solutions or features you've considered.
+-->
+
+**Additional context**
+<!--
+Add any other context or graphics (drag-and-drop an image) about the feature request here.
+-->

.github/ISSUE_TEMPLATE/003_rfc-proposal.md

@@ -0,0 +1,60 @@
+---
+name: RFC / Proposal
+about: Submit an RFC / Proposal
+title: ''
+labels: RFC
+assignees: ''
+
+---
+
+## Introduction
+
+<!--
+This section targets end users, TSC members, maintainers and anyone else that might
+need a quick explanation of your proposed change.
+-->
+
+### Problem description
+<!--
+Why do we want this change and what problem are we trying to address?
+-->
+
+### Proposed change
+<!--
+A brief summary of the proposed change - the 10,000 ft view on what it will
+change once this change is implemented.
+-->
+
+## Detailed RFC
+<!--
+In this section of the document the target audience is the dev team. Upon
+reading this section each engineer should have a rather clear picture of what
+needs to be done in order to implement the described feature.
+-->
+
+### Proposed change (Detailed)
+<!--
+This section is freeform - you should describe your change in as much detail
+as possible. Please also ensure to include any context or background info here.
+For example, do we have existing components which can be reused or altered.
+
+By reading this section, each team member should be able to know what exactly
+you're planning to change and how.
+-->
+
+### Dependencies
+<!--
+Highlight how the change may affect the rest of the project (new components,
+modifications in other areas), or other teams/projects.
+-->
+
+### Concerns and Unresolved Questions
+<!--
+List any concerns, unknowns, and generally unresolved questions etc.
+-->
+
+## Alternatives
+<!--
+List any alternatives considered, and the reasons for choosing this option
+over them.
+-->

.github/ISSUE_TEMPLATE/004_feature_request.md

@@ -0,0 +1,28 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: Feature Request
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+<!--
+A clear and concise description of what the problem is.
+-->
+
+**Describe the solution you'd like**
+<!--
+A clear and concise description of what you want to happen.
+-->
+
+**Describe alternatives you've considered**
+<!--
+A clear and concise description of any alternative solutions or features you've considered.
+-->
+
+**Additional context**
+<!--
+Add any other context or graphics (drag-and-drop an image) about the feature request here.
+-->