chore(mr-templates): Improve wording in "Developer Checklist" section(s)

.gitlab/merge_request_templates/Bugfix.md

@@ -44,14 +44,16 @@ Set labels:
 /label ~"Testautomation::👀"
 ```
 
-# 👷 Developer Checklist
+ # 👷 Developer Checklist
 
-- Does the MR include new bits and pieces (e.g. new secrets) that require documentation?
+**Documentation:**
-  - [ ] No.
-  - [ ] Yes, and the documentation was updated accordingly.
 
-Document in an extra comment and link to that comment:
+Does this MR introduce changes (e.g., new secrets, configuration options) that require documentation?
-- [ ] How you verified the fix is working as expected, also in upgrade scenarios.
+- [ ] No
-- [ ] Any regression testing done.
+- [ ] Yes, and the documentation has been updated accordingly
 
---> Link to comment:
+**Quality Assurance:**
+- [ ] Verified that the feature works as expected, including upgrade scenarios
+- [ ] Performed regression testing
+- Link to internal comment(s) with detailed QA results (to avoid exposing infrastructure details):
+  - ...

.gitlab/merge_request_templates/Feature.md

@@ -36,12 +36,14 @@ Set labels:
 
 # 👷 Developer Checklist
 
-- Does the MR include new bits and pieces (e.g. new secrets) that require documentation?
+**Documentation:**
-  - [ ] No.
-  - [ ] Yes, and the documentation was updated accordingly.
 
-Document in an extra comment and link to that comment:
+Does this MR introduce changes (e.g., new secrets, configuration options) that require documentation?
-- [ ] How you verified the feature is working as expected, also in upgrade scenarios.
+- [ ] No
-- [ ] Any regression testing done.
+- [ ] Yes, and the documentation has been updated accordingly
 
---> Link to comment:
+**Quality Assurance:**
+- [ ] Verified that the feature works as expected, including upgrade scenarios
+- [ ] Performed regression testing
+- Link to internal comment(s) with detailed QA results (to avoid exposing infrastructure details):
+  - ...

.gitlab/merge_request_templates/Other.md

@@ -30,12 +30,14 @@ Set labels:
 
 # 👷 Developer Checklist
 
-- Does the MR include new bits and pieces (e.g. new secrets) that require documentation?
+**Documentation:**
-  - [ ] No.
-  - [ ] Yes, and the documentation was updated accordingly.
 
-Document in an extra comment and link to that comment:
+Does this MR introduce changes (e.g., new secrets, configuration options) that require documentation?
-- [ ] How you verified the change is working as expected, also in upgrade scenarios.
+- [ ] No
-- [ ] Any regression testing done.
+- [ ] Yes, and the documentation has been updated accordingly
 
---> Link to comment:
+**Quality Assurance:**
+- [ ] Verified that the feature works as expected, including upgrade scenarios
+- [ ] Performed regression testing
+- Link to internal comment(s) with detailed QA results (to avoid exposing infrastructure details):
+  - ...

.gitlab/merge_request_templates/Update.md

@@ -28,14 +28,16 @@ Set labels:
 /label ~"Testautomation::👀"
 ```
 
-## 👷 Developer Checklist
+# 👷 Developer Checklist
 
-- Does the MR include new bits and pieces (e.g. new secrets) that require documentation?
+**Documentation:**
-  - [ ] No.
-  - [ ] Yes, and the documentation was updated accordingly.
 
-Document in an extra comment and link to that comment:
+Does this MR introduce changes (e.g., new secrets, configuration options) that require documentation?
-- [ ] How you verified the update is working as expected, also in upgrade scenarios.
+- [ ] No
-- [ ] Any regression testing done.
+- [ ] Yes, and the documentation has been updated accordingly
 
---> Link to comment:
+**Quality Assurance:**
+- [ ] Verified that the feature works as expected, including upgrade scenarios
+- [ ] Performed regression testing
+- Link to internal comment(s) with detailed QA results (to avoid exposing infrastructure details):
+  - ...