Add instructions for status-go PRs (#15225)

Define a process for status-go PRs as more of those are expected to be
opened by the Waku team.

.github/pull_request_template.md

@@ -21,6 +21,27 @@
 
 <!-- screenshot (or gif/video) that demonstrates the functionality, specially important if it's a bug fix. -->
 
+<!-- Uncomment this section for status-go upgrade/dogfooding pull requests
+
+### Impact on end user
+
+What is the impact of these changes on the end user (before/after behaviour)
+
+### How to test
+
+- How should one proceed with testing this PR.
+- What kind of user flows should be checked?
+
+### Risk 
+
+Described potential risks and worst case scenarios.
+
+Tick **one**:
+- [ ] Low risk: 2 devs MUST perform testing as specified above and attach their results as comments to this PR **before** merging.
+- [ ] High risk: QA team MUST perform additional testing in the specified affected areas **before** merging.
+
+-->
+
 ### Cool Spaceship Picture
 
-<!-- optional but cool ->
+<!-- optional but cool -->