Mention babel/rfcs in the "New feature" issue template (#11592)

* Mention babel/rfcs in the "New feature" issue template
* move npm issue to external gist, reword some issue template names and descriptions

Co-authored-by: Henry Zhu <hi@henryzoo.com>

.github/ISSUE_TEMPLATE/Feature_request.md

@@ -1,26 +1,22 @@
 ---
+
 name: "\U0001F680 Feature Request"
-about: "I have a suggestion (and may want to implement it \U0001F642)!"
+about: "I have a specific suggestion for Babel!"
-title: ''
+title: ""
-labels: 'i: enhancement, i: needs triage'
+labels: "i: enhancement, i: needs triage"
-assignees: ''
+assignees: ""
-
+---## Feature Request
----
-
-## Feature Request
 
 <!-- Check this if you would like to implement a PR, we are more than happy to help you go through the process !-->
+
 - [ ] I would like to work on this feature!
 
-**Is your feature request related to a problem? Please describe.**
+**Is your feature request related to a problem?**
-A clear and concise description of what the problem is. Ex. I have an issue when [...]
+A concise description of what the problem is. Ex. I have an issue when [...]
 
 **Describe the solution you'd like**
-A clear and concise description of what you want to happen. Add any considered drawbacks.
 
-**Describe alternatives you've considered**
+**Describe alternatives you've considered**.
-A clear and concise description of any alternative solutions or features you've considered.
 
-**Teachability, Documentation, Adoption, Migration Strategy**
+**Documentation, Adoption, Migration Strategy**
-If you can, explain how users will be able to use this and possibly write out a version the docs.
+If you can, explain how users will be able to use this and how it might be documented. Maybe a mock-up?
-Maybe a screenshot or design?

.github/ISSUE_TEMPLATE/Npm_error.md

@@ -1,16 +0,0 @@
----
-name: "\U0001F4E6 npm error"
-about: "When you get a `No matching version found for ...` error from npm"
-title: ''
-labels: 'i: npm cache'
-assignees: ''
-
----
-
-<!------------^ Click "Preview" for a nicer view!  -->
-
-First, check if the package for which `npm` throws an error is published by searching [on the npm website](https://www.npmjs.com/). If it is, then there is nothing that we can do about it: it was correctly published, but for some reason your package manager client doesn't find it.
-
-If you are using a proxy for the npm registry (maybe it's used by your company, or you are using it because your country blocks the main npm registry), then it's likely that it has cached the old version of the package and it isn't loading the new one. If you can, try clearing the proxy's cache. Otherwise, you will have to wait until the cache is automatically updated (it might take a few hours, or even days).
-
-If you are not using a proxy, or if it isn't a caching problem, please report the issue to npm (https://github.com/npm/cli/issues/new/choose) instead of in this repo!

.github/ISSUE_TEMPLATE/config.yml

@@ -1,8 +1,14 @@
 blank_issues_enabled: false
 contact_links:
-  - name: Ask a Question
+  - name: 📦 "No matching version found"
+    url: https://gist.github.com/hzoo/df94af2d2ec48696e683b772c775aa67
+    about: You may have an npm error related to proxies/caching.
+  - name: 🗣 Ask a Question, Discuss
     url: https://github.com/babel/babel/discussions
-    about: Ask any questions with the community!
+    about: How does X work 🤔? I made this! I have an idea..
-  - name: Support the Team!
+  - name: 💡 Propose an RFC
+    url: https://github.com/babel/rfcs
+    about: To suggest a new option or substantial change.
+  - name: 🤗 Support the Project
     url: https://github.com/sponsors/babel
-    about: Support the Babel project financially!
+    about: Support the Babel team financially.