NO-JIRA: Merge PR templates

Rename .github/PULL_REQUEST_TEMPLATE/console_pr.md -> .github/PULL_REQUEST_TEMPLATE.md.md and refactor its content: convert HTML headings to concise bold section labels, add Analysis/Root cause, Solution Description, Screenshots/screen recording, Test setup/test cases, and Browser conformance checkboxes, and reorganize reviewer/assignee guidance. Also delete .github/PULL_REQUEST_TEMPLATE/devconsole_pr.md. These changes standardize and expand the PR template to capture testing, design artifacts, and browser conformance information.

Author: logonoff

…thub/PULL_REQUEST_TEMPLATE/console_pr.md .github/PULL_REQUEST_TEMPLATE.md.github/PULL_REQUEST_TEMPLATE/console_pr.md renamed to .github/PULL_REQUEST_TEMPLATE.md .github/PULL_REQUEST_TEMPLATE/console_pr.md renamed to .github/PULL_REQUEST_TEMPLATE.md

@@ -1,4 +1,4 @@
-<h2 id="feature-fix">CONSOLE Features and Fixes:</h2>
+**Fixes**: https://redhat.atlassian.net/browse/
 <!--The pull request title must be prefixed with a Jira issue or Bugzilla bug in order to be merged. For example:
     For e.g Features: https://issues.redhat.com/browse/CONSOLE-XXXX
     - CONSOLE-XXXX: <title>
@@ -9,32 +9,38 @@
     Combos:
     - CONSOLE-XXXX, Bug XXXXXXX: <title>-->
 
-<h2 id="solution-description">Solution description</h2> 
-<!-- Describe your code changes in detail and explain the solution or functionality -->
+**Analysis / Root cause**:
+<!-- Briefly describe analysis of US/Task or root cause of Defect -->
 
-<h2 id="reviewers-and-assignees">Reviewers and assignees:</h2>
-<!-- 
+**Reviewers and assignees:**
+<!--
 - Tag an OCP console engineer to review the changes.
 - If there are visual, content, or interaction changes in the PR, tag "@openshift/team-ux-review"
 - If the PR is implementing a story, assign QE, docs, and PX approvers:
   Console Approver:
   /assign <gh-user>
 
-  QE approver:
-  /assign <gh-user>
-  
   Docs approver:
   /assign <gh-user>
-  
+
   PX approver:
   /assign <gh-user>
 -->
 
-<h2 id="test-cases">Test cases:</h2>
-<!-- Outline any test cases here -->
+**Solution Description**:
+<!-- Describe your code changes in detail and explain the solution or functionality -->
+
+**Screenshots / screen recording / design review**:
+<!-- Add screenshots or screen recordings for visual changes. Be sure to include before and after videos where relevant -->
+
+**Test setup / test cases:**
+<!-- If any setup required to test this PR, mention the details -->
 
-<h2 id="additional-info">Additional info:</h2>
+**Additional info:**
 <!-- Add any additional info here -->
 
-<h2 id="screenshots">Screen shots / gifs / design review:</h2>
-<!-- Add screenshots or gifs for visual changes. Be sure to include before and after where relevant -->
+**Browser conformance**:
+<!-- To mark tested browsers, use [x] -->
+- [ ] Chrome
+- [ ] Firefox
+- [ ] Safari