Update issue templates

.github/ISSUE_TEMPLATE/tools.md

@@ -0,0 +1,17 @@
+---
+name: Tools
+about: Report issues with the updaters, troubleshooter, or any other tools.
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+<!-- 
+Make sure to specify: 
+  - the name of the file (i.e. updater.bat, updater.sh)
+  - the OS where you used the tool (if applicable)
+  - steps to reproduce the issue
+  - expected result
+  - actual result
+-->

.github/ISSUE_TEMPLATE/troubleshooting-help.md

@@ -0,0 +1,35 @@
+---
+name: Troubleshooting help
+about: Ask for help troubleshooting issues with user.js
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+<!--
+Before you ask for help...
+  - Keep reading this. Seriously.
+  - Note that we do not support forks (i.e. IceCat, Pale Moon, WaterFox, etc).
+  - Make sure you searched for the setup tags in user.js.
+  - Search the GitHub repository. The information you need is most likely here already.
+  - See if you get the same problem in a new Firefox profile without user.js.
+  - See if you get the same problem without extensions/add-ons.
+  - Check out our wiki page on troubleshooting.
+    https://github.com/ghacksuserjs/ghacks-user.js/wiki/1.4-Troubleshooting
+
+See also:
+  - Extension breakage due to prefs
+    https://github.com/ghacksuserjs/ghacks-user.js/issues/391
+  - Prefs vs Recommended Extensions: Co-Existance+Enhancement | Conflicts
+    https://github.com/ghacksuserjs/ghacks-user.js/issues/350
+  - The extension CSP header modification game
+    https://github.com/ghacksuserjs/ghacks-user.js/issues/664
+	
+If you still need help, help us help you by providing relevant information:
+  - browser version
+  - Steps to Reproduce (STR)
+  - actual result
+  - expected result
+  - anything else you deem worth mentioning
+-->

.github/ISSUE_TEMPLATE/user-js.md

@@ -0,0 +1,13 @@
+---
+name: User.js
+about: Suggest changes to user.js
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+<!--
+We value feedback in general, but we value feedback from informed users more. There is no need for you to be an expert to participate (most of us aren't), but we hope that you at least understand our decisions before questioning them. We discuss all changes openly, and we do not make changes lightly. So, if you don't understand why we decided to add/remove/change a certain pref, search the repo. The answer is most certainly here.
+If some change we made took you by surprise (in the wrong way), remember that keeping track of changes is your responsibility. Watch the repo, read the changelogs, compare revisions as you update your copy of user.js, or use any other method you prefer.
+-->