Simplify github templates

Author: flyingsilverfin

.github/ISSUE_TEMPLATE/BUG_REPORT.md

@@ -7,35 +7,36 @@ assignees: ''
 
 ---
 
-Please replace every line in curly brackets { like this } with an appropriate answer, and remove this line.
-
 ## Description
 
-{ Please provide a clear and concise description of the bug. }
 
 ## Environment
 
-1. OS (where TypeDB server runs): { e.g. Mac OS 10, Windows 10, Ubuntu 16.4, etc. }
-2. TypeDB version (and platform): { e.g. TypeDB 1.4, or TypeDB Cluster 1.4.3 on Google Cloud }
-3. TypeDB driver: { e.g. driver-java, driver-python, driver-nodejs, driver-rust, or console }
-4. Other environment details:
+1. TypeDB distribution: Core/Enterprise/Cloud
+2. TypeDB version: 
+3. Environment: Linux/Mac/Windows/TypeDB Cloud/Google Cloud/AWS/Azure
+4. Driver version: 
+5. Other details:
 
 ## Reproducible Steps
 
-Steps to create the smallest reproducible scenario:
-1. { e.g. Run ... }
-2. { e.g. Load ... }
-3. { e.g. Query ... }
-4. { e.g. See error ... }
+1. Set up
+
+
+2. Execute
+
+
+3. Test/Query
 
-## Expected Output
 
-{ Please describe what you expected to happen. }
+4. Unexpected result
+
+
+
+## Expected result
 
-## Actual Output
 
-{ Please describe what actually happened. }
- 
 ## Additional information
 
-{ Any additional information, including logs or screenshots if you have any. }
+Relevant logs from TypeDB or Driver:
+

.github/ISSUE_TEMPLATE/FEATURE_REQUEST.md

@@ -1,26 +1,17 @@
 ---
 name: Feature Request
 about: Request a feature here, or visit forum.typedb.com for ideas and questions
-title: ''
 labels: feature
-assignees: ''
-
 ---
 
-Please replace every line in curly brackets { like this } with appropriate answers, and remove this line.
-
 ## Problem to Solve
 
-{ Please describe the problem you would like to solve. }
 
 ## Current Workaround
 
-{ Please describe how you currently solve or work around this problem, given TypeDB's limitation. }
 
 ## Proposed Solution
 
-{ Please describe the solution you would like TypeDB to provide, to solve the problem above. }
 
 ## Additional Information
 
-{ Any additional information, including logs or screenshots if you have any. }

.github/ISSUE_TEMPLATE/REFACTOR.md

@@ -4,12 +4,8 @@ about: Propose an architecture refactor here
 labels: refactor
 ---
 
-Please replace every line in curly brackets { like this } with appropriate answers, and remove this line.
-
 ## Problem to Solve
 
-{ Please describe the problem with the current architecture that you would like to solve. }
 
 ## Proposed Solution
 
-{ Please describe how you would like to change the architecture, to solve the problem above. }

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,17 +1,4 @@
-**For the title of this PR:** please follow the grammatical rules of a usual publication title, without capitalisation (except for the first letter). Thus, the title should NOT CONTAIN CODE: no dots, no parentheses, no backticks, no brackets, etc. It needs to be distinctive (not detailed) and succinct (not lengthy). Details of this PR will go in the description. **For the description of this PR:** please replace every line in curly brackets ( { like this } ) with an appropriate description following the guidance. Finally, **please remove this paragraph**.
+## Release notes: usage and product changes
 
-## What is the goal of this PR?
 
-{ In the form of a paragraph (only use bullet points if strictly necessary), please describe the goal of this PR, why they are valuable to achieve, and reference the related GitHub issues. This section will be automatically compiled into the release notes, so please:
-  - describe the impact of the change in this PR to the _user_ of this repository (e.g. end user, contributor, developer).
-  - describe the new product behaviour in _present tense_, and the old behaviour and how it's been changed in _past tense_.
-  - Use the _Royal We_: _"We"_ made changes, not _"I"_ made changes. }
-
-## What are the changes implemented in this PR?
-
-{ Please explain what you implemented, why your changes are the best way to achieve the goal(s) above. Please describe every method, class and package, by explaining:
-  - its responsibility, 
-  - how it's expected to behave, and 
-  - how it relates to the adjacent methods/classes/packages it interacts with. 
-
-This would allow the reviewer to understand your intentions in the code much better. If you're adding new classes, make sure these explanations are also included in the class header comments. Last but not least, please reference the GitHub issues to be automatically closed, such like 'closes #number'. }
+## Implementation