Adds github issue templates (#555)

Co-authored-by: marcinc <[email protected]>

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,40 @@
+---
+name: Bug report
+about: Help us identify and fix issues in Kev
+title: "[BUG]"
+labels: bug
+assignees: ''
+
+---
+
+<!--
+Thank you for helping to improve Kev!
+
+Please search open issues before raising a new one. This project uses issues to
+track both bugs and new features.
+-->
+
+### Short issue description
+<!--
+Please let us know what behaviour you expected and how Kev actually behaved.
+-->
+
+Kev version:
+OS (Linux/Mac/Windows..):
+Docker Compose version:
+Kubernetes version:
+Kubernetes distribution (e.g. GKE, EKS, ...):
+
+
+### How can we reproduce the issue?
+<!--
+Give us instructions on how to reproduce the bug as briefly and precisely as possible.
+Example manifests, docker-compose files used or any other related files that might help
+us identify issues will be much appreciated.
+-->
+
+### Suggestions on how to fix the issue (OPTIONAL)
+<!--
+If you've got any suggestions or remarks on how best to address this issues please leave
+some comments here. Thank you.
+-->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,28 @@
+---
+name: Feature request
+about: Suggest an idea for improvement or new feature
+title: "[FR]"
+labels: enhancement
+assignees: ''
+
+---
+
+### Is your feature request related to a problem? Please describe.
+<!--
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+-->
+
+### 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 screenshots about the feature request here.
+-->