Form templates (metaplex-foundation#283)

* chore(issue-template): add bug report form

* chore(issue-template): add pr template

* chore(issue-template): convert pr template to markdown

* chore(issue template): change file extension

* refactor(form templates): add feature request issue form; make minor changes

* fix(form template): fix boolean options

Author: samuelvanderwaal

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,57 @@
+name: Bug report
+title: "[Bug]: "
+description: Report incorrect or unexpected behavior
+labels: [bug]
+body:
+  - type: dropdown
+    id: package
+    attributes:
+      label: Which package is this bug report for?
+      options:
+        - auction-house
+        - auction
+        - candy-machine
+        - core
+        - fixed-price-sale
+        - gumdrop
+        - metaplex
+        - nft-packs
+        - token-entangler
+        - token-metadata
+        - token-vault
+    validations:
+      required: true
+  - type: textarea
+    id: description
+    attributes:
+      label: Issue description
+      description: |
+        Describe the issue in as much detail as possible.
+
+        Tip: You can attach images or log files by clicking this area to highlight it and then dragging files into it.
+      placeholder: |
+        Steps to reproduce with:
+        1. do thing
+        2. observe behavior
+        3. see error logs below
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
+      render: shell
+    validations:
+      required: false
+  - type: dropdown
+    id: priority
+    attributes:
+      label: Priority this issue should have
+      description: Please be realistic. If you need to elaborate on your reasoning, please use the Issue description field above.
+      options:
+        - Low (slightly annoying)
+        - Medium (should be fixed soon)
+        - High (immediate attention needed)
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,58 @@
+name: Feature request
+description: Request a new feature
+title: "[Feature]: "
+labels: [enhancement]
+body:
+  - type: dropdown
+    id: package
+    attributes:
+      label: Which package is this feature request for?
+      options:
+        - auction-house
+        - auction
+        - candy-machine
+        - core
+        - fixed-price-sale
+        - gumdrop
+        - metaplex
+        - nft-packs
+        - token-entangler
+        - token-metadata
+        - token-vault
+    validations:
+      required: true
+  - type: textarea
+    id: description
+    attributes:
+      label: Feature
+      description: A clear and concise description of what the problem is, or what feature you want to be implemented.
+      placeholder: I'm always frustrated when..., A good addition would be...
+    validations:
+      required: true
+  - type: dropdown
+    id: standard-change
+    attributes:
+      label: Standard Change?
+      options:
+        - "No"
+        - "Yes"
+      description: Does this feature change the Metaplex token standard in a fundamental way?
+    validations:
+      required: true
+  - type: textarea
+    id: solution
+    attributes:
+      label: Ideal solution or implementation
+      description: A clear and concise description of what you want to happen.
+    validations:
+      required: true
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternative solutions or implementations
+      description: A clear and concise description of any alternative solutions or features you have considered.
+  - type: textarea
+    id: additional-context
+    attributes:
+      label: Other context
+      description: Any other context, screenshots, or file uploads that help us understand your feature request.

.github/PULL_REQUEST_TEMPLATE/pr_template.md

@@ -0,0 +1,13 @@
+### Note
+Pull Requests that make fundamental changes to the Metaplex standard are unlikely to be accepted without a discussion first. Please open a feature request issue instead to discuss your desired changes. We are working on a more formal process for proposing changes to the Metaplex standard.
+
+It's much easier for us to read and review a PR that is small, linted, and contains only one material enhancement. If your PR is very large and encompasing many features consider breaking it up in to a few PRs so we can digest the information in each pr with more accuracy.
+
+### Description
+Describe the purpose of and changes within this Pull Request.
+
+### References
+List links to any related tasks (GitHub Issues, Pull Requests, 3rd part task managers)
+
+### Testing
+How was this tested? If manually tested, list all steps necessary for the reviewer to confirm.