chore: keep issue and pr templates in sync

Signed-off-by: Mark Sagi-Kazar <mark.sagikazar@gmail.com>

.github/ISSUE_TEMPLATE/bug_report.md

@@ -9,23 +9,25 @@ Thank you for sending a bug report! Here are some tips:
 2. If you are not sure if it is a bug or not, you can ask in the Kubernetes slack channel `#dexidp`.
 -->
 
-**Expected behavior (what you expected to happen)**:
+#### Expected behavior (what you expected to happen)
 
-**Actual behavior (what actually happened)**:
+#### Actual behavior (what actually happened)
+
+#### Steps to reproduce
 
-**Steps to reproduce**:
 1. ...
 2. ...
 3. ...
 
-**Environment**:
+#### Environment
+
 - Dex version:
 - Storage type:
 - Installation type (official docker image, helm chart, etc.):
 
-**Anything else we should know?**:
+#### Anything else we should know?
 
-**Additional information for debugging (if necessary)**:
+#### Additional information for debugging (if necessary)
 
 <details><summary>Configuration</summary><br><pre>
 

.github/ISSUE_TEMPLATE/feature_request.md

@@ -7,14 +7,14 @@ about: Suggest an idea for Dex
  Please describe what you would like to change/add and why in detail by filling out the template below.
  -->
 
-**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'm always frustrated when [...] -->
 
-**Describe the solution you'd like to see**
+#### Describe the solution you'd like to see
 <!-- A clear and concise description of what would you like to happen. -->
 
-**Describe alternatives you've considered**
+#### Describe alternatives you've considered
 <!-- A clear and concise description of any alternative solutions or features you've considered. -->
 
-**Additional context**
+#### Additional context
 <!-- Add any other context or screenshots about the feature request here. -->