gitlab, issue-templates: Drop "Feature" and "Epic" templates

Those aren't actionable for our users. Most of the information required
in these templates are for developers or designers familiar with the
development process.

.gitlab/issue_templates/Epic.md

@@ -1,41 +0,0 @@
-# Current problems
-<!--
-What are the problems that the current project has?
-
-For example:
-* User cannot use the keyboard to perform most common actions
-or
-* User cannot see documents from cloud services
--->
-
-# Goals & use cases
-<!--
-What are the use cases that this proposal will cover? What are the end goals?
-
-For example:
-* User needs to share a file with their friends.
-or
-* It should be easy to edit a picture within the app.
--->
-
-# Requirements
-<!--
-What does the solution needs to ensure for being succesful?
-
-For example:
-* Work on small form factors and touch
-or
-* Use the Meson build system and integrate with it
--->
-
-# Relevant art
-<!--
-Is there any product that has implemented something similar? Put links to other
-projects, pictures, links to other code, etc.
--->
-
-# Proposal & plan
-<!-- What's the solution and how should be achieved? It can be split in smaller
-tasks of minimum change, so they can be delivered across several releases. -->
-
-/label ~"1. Epic"

.gitlab/issue_templates/Feature.md

@@ -1,27 +0,0 @@
-<!--
-
-Not following the communication guidelines [1] will mean your issue or comment
-will be removed. Read it carefully before submitting this issue.
-
-
-[1] https://gitlab.gnome.org/GNOME/gnome-control-center/blob/main/docs/CODE_OF_CONDUCT.md#communication-guidelines
-
- -->
-
-Detailed description of the feature. Put as much information as you can.
-
-Proposed Mockups:
-
-(Add mockups of the proposed feature)
-
-## Design Tasks
-
-* [ ]  design tasks
-
-## Development Tasks
-
-* [ ]  development tasks
-
-## QA Tasks
-
-* [ ]  qa (quality assurance) tasks