Add issue template for Turbopack (vercel#120)

You can preview these here:

-
https://github.com/vercel/the-three-body/blob/mehulkar/turbo-368-add-new-turbopack-issue-template/.github/ISSUE_TEMPLATE/0-turborepo-bug-report.yml
-
https://github.com/vercel/the-three-body/blob/mehulkar/turbo-368-add-new-turbopack-issue-template/.github/ISSUE_TEMPLATE/1-turbopack-bug-report.yml
-
https://github.com/vercel/the-three-body/blob/mehulkar/turbo-368-add-new-turbopack-issue-template/.github/ISSUE_TEMPLATE/2-feature-request.yml
- Not sure why this is giving an error saying "Name must be unique".
It's possible it's clashing with the template in `staging` branch, but
since the filename is changed, it thinks there's a problem?

You can also test out a repro of this in a sample repro if you want to
see the end result, since you can't really preview it until it's merged:
https://github.com/mehulkar/testing-gh-issue-templates/issues/new/choose

.github/ISSUE_TEMPLATE/-bug_report.yml → .github/ISSUE_TEMPLATE/0-turborepo-bug-report.yml

@@ -1,6 +1,7 @@
-name: Bug Report
+name: Turborepo Bug Report
 description: Create a bug report for the Turborepo team
-labels: "template: bug"
+title: "[turborepo] "
+labels: ["kind: bug"]
 body:
   - type: markdown
     attributes:
@@ -40,7 +41,7 @@ body:
   - type: textarea
     attributes:
       label: Describe the Bug
-      description: A clear and concise description of what the bug is.
+      description: A clear and concise description of the bug.
     validations:
       required: true
   - type: textarea
@@ -55,6 +56,12 @@ body:
       description: Steps to reproduce the behavior, please provide a clear code snippets that always reproduces the issue or a GitHub repository. Screenshots can be provided in the issue body below.
     validations:
       required: true
+  - type: input
+    attributes:
+      label: Reproduction Repo
+      description: Include a URL to a repository that reproduces this issue. This is optional, but increases the likelihood that we can help you!
+    validations:
+      required: false
   - type: markdown
     attributes:
       value: Before posting the issue go through the steps you've written down to make sure the steps provided are detailed and clear.

.github/ISSUE_TEMPLATE/1-turbopack-bug-report.yml

@@ -0,0 +1,75 @@
+# This is the same as the Turborepo bug report template at the moment,
+# but it's a different template in case we want to customize it further and get different inputs.
+name: Turbopack Bug Report
+description: Create a bug report for the Turbopack team
+title: "[Turbopack] "
+labels: ["kind: bug"]
+body:
+  - type: markdown
+    attributes:
+      value: Thanks for taking the time to file a bug report! Please fill out this form as completely as possible.
+  - type: markdown
+    attributes:
+      value: If you leave out sections there is a high likelihood it will be moved to the GitHub Discussions "Help" section.
+  - type: input
+    attributes:
+      label: What version of Turbopack are you using?
+      description: "For example: 1.0.0"
+    validations:
+      required: true
+  - type: dropdown
+    id: packageManager
+    attributes:
+      multiple: true
+      label: What package manager are you using / does the bug impact?
+      options:
+        - npm
+        - pnpm
+        - Yarn v1
+        - Yarn v2/v3 (node_modules linker only)
+    validations:
+      required: true
+  - type: dropdown
+    id: os
+    attributes:
+      label: What operating system are you using?
+      options:
+        - Mac
+        - Windows
+        - Linux
+        - Other
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Describe the Bug
+      description: A clear and concise description of the bug.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Expected Behavior
+      description: A clear and concise description of what you expected to happen.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: To Reproduce
+      description: Steps to reproduce the behavior, please provide a clear code snippets that always reproduces the issue or a GitHub repository. Screenshots can be provided in the issue body below.
+    validations:
+      required: true
+  - type: input
+    attributes:
+      label: Reproduction Repo
+      description: Include a URL to a repository that reproduces this issue. This is optional, but increases the likelihood that we can help you!
+    validations:
+      required: false
+  - type: markdown
+    attributes:
+      value: Before posting the issue go through the steps you've written down to make sure the steps provided are detailed and clear.
+  - type: markdown
+    attributes:
+      value: Contributors should be able to follow the steps provided in order to reproduce the bug.
+  - type: markdown
+    attributes:
+      value: Thanks in advance!

.github/ISSUE_TEMPLATE/1.feature-request.yml → .github/ISSUE_TEMPLATE/2-feature-request.yml

@@ -1,13 +1,23 @@
 name: Feature Request
-description: Create a feature request for Turborepo
-labels: "template: story"
+description: Create a feature request
+labels: ["story"]
 body:
   - type: markdown
     attributes:
       value: Thanks for taking the time to file a feature request! Please fill out this form as completely as possible.
   - type: markdown
     attributes:
       value: 'Feature requests will be converted to the GitHub Discussions "Ideas" section.'
+  - type: dropdown
+    id: project
+    attributes:
+      multiple: false
+      label: Which project is this feature idea for?
+      options:
+        - Turborepo
+        - Turbopack
+    validations:
+      required: true
   - type: textarea
     attributes:
       label: Describe the feature you'd like to request