remove issue templates in favor of discussion links

.github/ISSUE_TEMPLATE/feature-request.md

@@ -1,22 +0,0 @@
----
-name: Feature enhancement or request
-about: Improvements or ideas for GriefPrevention
-title: Name of feature goes here. No brackets, please.
-labels: Add-on Suggestion
-assignees: ''
-
----
-
-**As** a player
-**I want** to capture animals in a snowball
-**Because** I wanna be the very best, Like no one ever was.
-
-Here's how to increase your chances of your feature request being understood (and potentially considered for implementation): https://content.pivotal.io/blog/how-to-write-well-formed-user-stories
-
-Optional questions:
-
-**Is your feature request related to a problem? Please describe.**
-A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
-
-**Describe alternatives you've considered**
-A clear and concise description of any alternative solutions or features you've considered.

.github/ISSUE_TEMPLATE/question.md

@@ -1,28 +0,0 @@
----
-name: Question
-about: Got a question?
-title: Summarize your question into a single sentence here
-labels: Question
-assignees: ''
-
----
-
-The answer to your question may exist in the wiki, go check that out first! 
-
-Wiki: https://github.com/TechFortress/GriefPrevention/wiki
-
-Otherwise, if you have a spigot account, you may have better luck posting in the discussion thread so people who follow the thread may see your question. https://www.spigotmc.org/threads/griefprevention.35615/page-311
-
-Still no luck? Really? Then go ahead and ask here.
-
-Please remember to provide as much detail as you can - smart questions are
-much more likely to be answered.  See "Asking questions the smart way":
-http://www.catb.org/~esr/faqs/smart-questions.html
-
-As an open-source project, we're all volunteers with limited time to spend,
-so providing enough info (including any error messages etc) up-front makes
-it more likely we can provide you an answer with limited time.
-
-
-
-