Provide issue templates (#253)

Created the first set of issue-creation templates for Durable Python. Gave them some personality with some emojis here and there.

Author: davidmrdavid

.github/ISSUE_TEMPLATE/----feature-request.md

@@ -0,0 +1,19 @@
+---
+name: "\U0001F4A1  Feature request"
+about: Suggest an idea for this project!
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+💡 **Feature description**
+> What would you like to see, and why?
+> What kinds of usage do you expect to see in this feature?
+
+💭 **Describe alternatives you've considered**
+> What are other ways to achieve this? Have you thought of alternative designs or solutions?
+> Any existing workarounds? Why are they not sufficient? We'd like to know!
+
+**Additional context**
+> Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/---bug-report.md

@@ -0,0 +1,31 @@
+---
+name: "\U0001F41B Bug report"
+about: Did something not work out as expected? Let us know!
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+🐛 **Describe the bug**
+> A clear and concise description of what the bug is. 
+
+🤔 **Expected behavior**
+> What should have happened?
+
+☕ **Steps to reproduce**
+> What Durable Functions patterns are you using, if any?
+> Any minimal reproducer we can use?
+> Are you running this locally or on Azure? 
+
+⚡**If deployed to Azure**
+> We have access to a lot of telemetry that can help with investigations. Please provide as much of the following information as you can to help us investigate!
+
+- **Timeframe issue observed**:
+- **Function App name**:
+- **Function name(s)**:
+- **Azure region**:
+- **Orchestration instance ID(s)**:
+- **Azure storage account name**:
+
+> If you don't want to share your Function App or storage account name GitHub, please at least share the orchestration instance ID. Otherwise it's extremely difficult to look up information.