chore: add pr and issue templates (#392)

Author: iartemiev

.changeset/cuddly-trains-remember.md

@@ -0,0 +1,2 @@
+---
+---

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -0,0 +1,47 @@
+name: Bug Report
+description: Create a bug report to help us improve `@aws-amplify/data-schema`
+labels: ['pending-triage']
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report!
+  - type: textarea
+    id: env
+    attributes:
+      label: Package version
+      description: |
+        Please copy and paste the output of the following command.
+        ```bash
+        npm ls @aws-amplify/data-schema
+        ```
+      render: plain text
+    validations:
+      required: true
+  - type: textarea
+    id: env
+    attributes:
+      label: Schema definition
+      description: |
+        Please copy and paste the contents of `amplify/data/resource.ts` below
+      render: plain text
+    validations:
+      required: false
+  - type: textarea
+    id: description
+    attributes:
+      label: Describe the bug
+      description: |
+        A clear and concise description of the bug you are observing.
+    validations:
+      required: true
+  - type: textarea
+    id: reproduction
+    attributes:
+      label: Reproduction steps
+      description: |
+        How can this bug be reproduced?
+        Please include any code snippets or screenshots that you think would be helpful!
+        For more complex issues provide a repository with the smallest sample that reproduces the issue.
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Ask the Community
+    url: https://discord.gg/invite/amplify
+    about: Check out the help channel on Amplify's community Discord to ask your questions about building applications with Amplify.

.github/ISSUE_TEMPLATE/feature-request.yml

@@ -0,0 +1,35 @@
+name: Feature Request
+description: Suggest an idea to help us improve `@aws-amplify/data-schema`
+labels: ['pending-triage']
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this feature request!
+   - type: textarea
+    id: env
+    attributes:
+      label: Package version
+      description: |
+        Please copy and paste the output of the following command.
+        ```bash
+        npm ls @aws-amplify/data-schema
+        ```
+      render: plain text
+    validations:
+      required: true
+  - type: textarea
+    id: description
+    attributes:
+      label: Describe the feature
+      description: A clear and concise description of the feature you are proposing.
+    validations:
+      required: true
+  - type: textarea
+    id: use-case
+    attributes:
+      label: Use case
+      description: |
+        Please provide information about your use case and how this feature will help with it.
+    validations:
+      required: true

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,44 @@
+<!--
+Thank you for your Pull Request! Please describe the problem this PR fixes and a summary of the changes made.
+Link to any relevant issues, code snippets, or other PRs.
+
+For trivial changes, this template can be ignored in favor of a short description of the changes.
+-->
+
+## Problem
+
+<!--
+Describe the issue this PR is solving
+-->
+
+**Issue number, if available:**
+
+## Changes
+
+<!--
+Summarize the changes introduced in this PR. This is a good place to call out critical or potentially problematic parts of the change.
+-->
+
+**Corresponding docs PR, if applicable:**
+
+## Validation
+
+<!--
+Describe how changes in this PR have been validated. This may include added or updated unit, integration and/or E2E tests, test workflow runs, or manual verification. If manual verification is the only way changes in this PR have been validated, you will need to write some automated tests before this PR is ready to merge.
+
+For changes to test infra, or non-functional changes, tests are not always required. Instead, you should call out _why_ you think tests are not required here.
+
+If changes affect a GitHub workflow that is not included in the PR checks, include a link to a passing test run of the modified workflow.
+--->
+
+## Checklist
+
+<!--
+These items must be completed before a PR is ready to be merged.
+Feel free to publish a draft PR before these items are complete.
+-->
+
+- [ ] If this PR includes a functional change to the runtime or type-level behavior of the code, I have added or updated automated test coverage for this change. (see [Testing Strategy README](../TESTING-STRATEGY.md))
+- [ ] If this PR requires a docs update, I have linked to that docs PR above.
+
+_By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license._