chore: update issue templates (#84)

<!-- markdownlint-disable MD041 -->
#### What this PR does / why we need it
We noticed that we need a lot of roundtrips on bug reports with our
users to get all the information we need to identify and reproduce their
bugs. We hope to be able to reduce those roundtrips by providing a more
verbose description of what we expect in our issue template.

Besides, we remove the issue templates merely used for our project
management from these issue templates (that are propagated to all our
repositories). Instead, we will add them only to `ocm-project`.

#### Which issue(s) this PR is related to
<!--
Usage: `Related to #<issue number>`, or `Related to (paste link of
issue)`.
-->

---------

Signed-off-by: Fabian Burth <[email protected]>
Co-authored-by: Steffen <[email protected]>

Author: fabianburth

.github/ISSUE_TEMPLATE/bug.md

@@ -8,28 +8,50 @@ assignees: ''
 ---
 
 **Context**
-A clear and concise description of what the bug is.
+<!---
+Please provide a clear and concise description of the bug.
+-->
 
 **Version**
-v0.20.0
+<!---
+Please provide the version of the project are you using?
+- For ocm-cli, run `ocm --version`.
+- For ocm-controllers, check the image specified in your deployment.
+-->
 
 **To Reproduce**
-Steps to reproduce the behavior:
-
+<!---
+Please provide steps to reproduce the behavior. Keep the description as 
+minimal and precisely as possible! 
+The listed information below is intended as guidance, please include only as 
+much as required to reproduce.
+
+- For the ocm-cli, provide information about
+  - the environment you are running on (OS, shell, etc.),
+  - the commands (including flags) you used,
+  - the relevant parts of your configuration file (default location `$HOME/.
+ocmconfig`). Be careful to redact any sensitive information.
+
+- For the ocm-controllers, provide information about
+  - the relevant kubernetes resource manifests
+  - the relevant ocm components and artifacts (an overview can be provided 
+    by `ocm get cv ... -r` and `ocm get resources ... -r`)
+  - the relevant controller logs
+  - the cluster infrastructure you are running on (like kind)
+  - the kubernetes/kro/flux version
+-->
 
 **Actual behavior**
-A clear and concise description of what is happening.
+<!---
+Please provide a clear and concise description of what actually happened.
+-->
 
 **Expected behavior**
-A clear and concise description of what you expected to happen.
-
-**Screenshots (optional)**
-If applicable, add screenshots to help explain your problem.
-
-**Environment**
-- [ ] windows
-- [ ] linux
-- [x] mac
+<!---
+Please provide a clear and concise description of what you expected to happen.
+-->
 
 **Additional Comments**
-Any observation, gut feeling or other information you think help the community to troubleshoot the problem?
+<!---
+Is there any other information we need to know about this bug?
+-->

.github/ISSUE_TEMPLATE/epic.md

@@ -7,4 +7,8 @@ labels: kind/feature
 ---
 
 **Description**
-What would you like to be added? Why is this needed?
+<!---
+What would you like to be added?
+Why is this needed?
+-->
+