Add templates for Pull Requests and Issues (rust-lang#81)

Author: adpaco-aws

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,37 @@
+---
+name: Bug Report
+about: Create a bug report for RMC
+labels: bug
+---
+<!--If you discover a potential security issue in RMC we ask that you notify
+AWS Security via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/).
+Please do **not** create a public github issue.
+-->
+<!--
+Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
+along with any information you feel relevant to replicating the bug.
+-->
+
+I tried this code:
+<!-- If the code fits into a single file, please post it here. Otherwise please
+post a link to the repository and branch that exposes the issue
+-->
+```rust
+<code>
+```
+
+using the following command line invocation:
+
+```
+<command>
+```
+
+with RMC version:
+
+I expected to see this happen: *explanation*
+
+<!--
+If RMC crashed, please include a backtrace in the code block by setting
+`RUST_BACKTRACE=1` in your environment. E.g. `RUST_BACKTRACE=1 rmc ...`
+-->
+Instead, this happened: *explanation*

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,25 @@
+---
+name: Feature Request
+about: Create a feature request for RMC
+labels: 
+---
+<!--If you discover a potential security issue in RMC we ask that you notify
+AWS Security via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/).
+Please do **not** create a public github issue.
+-->
+<!--
+Thank you for requesting an RMC feature! Please include the
+following information if it applies to your case
+-->
+Requested feature:
+Use case:
+Link to relevant documentation (Rust reference, Nomicon, RFC):
+Is this a breaking change?
+
+Test case:
+<!-- If the code fits into a single file, please post it here. Otherwise please
+post a link to the repository and branch that exposes the issue
+-->
+```rust
+<code>
+```

.github/ISSUE_TEMPLATE/performance_issue.md

@@ -0,0 +1,34 @@
+---
+name: Performance Issue
+about: Create a performance issue for RMC
+labels: bug
+---
+<!--If you discover a potential security issue in RMC we ask that you notify
+AWS Security via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/).
+Please do **not** create a public github issue.
+-->
+<!--
+Thank you for filing a performance issue! Please provide a short summary of the issue,
+along with any information you feel relevant to replicating the issue.
+-->
+
+I tried this code:
+<!-- If the code fits into a single file, please post it here. Otherwise please
+post a link to the repository and branch that exposes the issue
+-->
+```rust
+<code>
+```
+
+using the following command line invocation:
+
+```
+<command>
+```
+
+with RMC version:
+
+If this is a performance regression, how long did it use to take?
+Otherwise how much did you expect it to take?
+How long did it take?
+What stage appears to be the slowest (compilation, verification, code coverage)?

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,26 @@
+
+### Resolved issues:
+
+ resolves #ISSUE-NUMBER
+
+### Description of changes: 
+
+Describe RMC's current behavior and how your code changes that behavior. If there are no issues this PR is resolving, explain why this change is necessary.
+
+### Call-outs:
+
+<!-- Address any potentially confusing code. Is there code added that needs to be cleaned up later? Is there code that is missing because it’s still in development? 
+-->
+### Testing:
+
+ How is this change tested?
+
+ Is this a refactor change?
+
+### Checklist
+- [ ] Each commit message has a non-empty body, explaining why the change was made
+- [ ] Methods or procedures are documented
+- [ ] Regression or unit tests are included, or existing tests cover the modified code
+- [ ] My PR is restricted to a single feature or bugfix
+
+By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.