chore: Add issue templates

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,53 @@
+---
+name: "\U0001F41B Bug"
+about: Something is crashing or not working as intended
+labels: bug
+
+---
+
+## Environment
+
+**Package version:**  
+
+<details>
+  <summary>Flutter doctor</summary>
+
+<!-- Paste the output of running `flutter doctor -v` below inside ``` and ``` -->
+```
+```
+
+</details>
+
+<details>
+  <summary>Code sample</summary>
+
+<!--
+      Please create a minimal reproducible sample that shows the problem
+      and attach it below between the lines with the backticks.
+
+      You can use a example code or Flutter sample app
+
+      Without this we will unlikely be able to progress on the issue, and because of that
+      we regretfully will have to close it.
+-->
+
+```dart
+```
+
+</details>
+
+## Description
+
+**Expected behavior:**
+
+**Current behavior:**
+
+## Steps to reproduce
+
+1. This
+2. Than that
+3. Then
+
+## Images <!-- if available, else delete -->  
+
+## Stacktrace/Logcat <!-- if available, else delete -->  

.github/ISSUE_TEMPLATE/documentation.md

@@ -0,0 +1,18 @@
+---
+name: "\U0001F4C3 Documentation Bug"
+about: You want to report something that is wrong or missing from the documentation.
+labels: documentation
+
+---
+
+### Describe the change you would like to see
+<!-- A clear and concise description of the bug or documentation you feel is missing.
+For example: The Technical Reference does not include information about the FormBuilderFilterChip widget. -->
+
+### How would the suggested change make the documentation more useful?
+<!-- Provide context for how the requested change would make the docs easier to use and improve your ability to develop successful applications with this packages.
+For example: It's hard to know a method exists or understand its use when you have to search through the code base to learn about it. Properly documenting it in the Technical Reference makes it easier for me to know what the flutter_fom_builder is (and is not capable of).  -->
+
+### Additional context
+<!-- Add any other context about your feedback here. 
+For example: I am reading the docs directly from GitHub, so it's harder for me to find information on a particular method if it's not included in the documentation. -->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,18 @@
+---
+name: "\U0001F680 Feature request"
+about: Suggest new feature or request for this project
+labels: enhancement
+
+---
+
+## Environment
+
+**Package version:**
+
+## Description
+
+**What you'd like to happen:**
+
+**Alternatives you've considered:** <!-- if available, else delete -->  
+
+**Images:** <!-- if available, else delete -->  

.github/ISSUE_TEMPLATE/question.md

@@ -0,0 +1,14 @@
+---
+name: "\U0001F914 Questions and Help"
+about: You have a quetion or need help using this packages
+labels: question
+
+---
+
+## Environment
+
+**Package version:**
+
+## Describe your question
+<!-- A clear and concise description of your question or help wanted.
+For example: How can I add a datetime field? -->