docs(templates): update issues templates and add documentation check

.github/ISSUE_TEMPLATE/bug.md

@@ -20,6 +20,6 @@ labels: bug
 
 ### Additional Information
 
-- Status desktop version:
-- Operating System:
+- Status app version:
+- Operating System and version:
 

.github/ISSUE_TEMPLATE/feature-issue.md

@@ -5,7 +5,7 @@ labels: feature
 ---
 
 <!-- Note -->
-<!-- Generally feature requests should go to https://github.com/status-im/feature-specs -->
+<!-- Generally feature requests should go to https://discuss.status.app/c/features/51 -->
 <!-- Note -->
 
 ### Description
@@ -14,10 +14,6 @@ labels: feature
 [comment]: # (Describe the use cases the implementation should cover. E.g. New users, existing users, public chat, group chat, etc)
 *Summary*: ...
 
-### Metrics
-
-Does that feature need metrics to be added? If yes, describe which events should be tracked and add them to Mixpanel
-
 ### Acceptance Criteria
 
 [comment]: # (Rules for the future PR to be accepted.)

.github/pull_request_template.md

@@ -6,10 +6,11 @@
 
 <!-- List the affected areas (e.g wallet, browser, etc..) -->
 
-### Architecture compliance
+### Quality checklist
 
 - [ ] I am familiar with the [application architecture](/docs/architecture.md) and agreed good practices.
 My PR is consistent with this document: [QML Architecture Guidelines](/guidelines/QML_ARCHITECTURE_GUIDE.md)
+- [ ] I have updated the necessary documentation if needed (eg: updated BUILDING.md if I updated dependencies)
 
 ### Screencapture of the functionality
 
@@ -21,8 +22,8 @@ My PR is consistent with this document: [QML Architecture Guidelines](/guideline
 
 ### How to test
 
-- <!-- How should one proceed with testing this PR. -->
-- <!-- What kind of user flows should be checked? -->
+<!-- How should one proceed with testing this PR. -->
+<!-- What kind of user flows should be checked? -->
 
 ### Risk