Update pull_request_template.md with new checks (#21127)

Author: sanjuyadav24

.github/pull_request_template.md

@@ -19,6 +19,23 @@ _Assess the level of risk and provide reasoning (e.g., scope, impact, backward c
 
 ---
 
+### **Change Behind Feature Flag** (Yes / No)
+_Can this change be behine feature flag, if not why?_
+
+---
+
+### **Tech Design / Approach**
+- Design has been written and reviewed. 
+- Any architectural decisions, trade-offs, and alternatives are captured. 
+
+---
+
+### **Documentation Changes Required** (Yes/No)
+_Indicate whether related documentation needs to be updated._
+- User guides, API specs, system diagrams, or runbooks are updated. 
+
+---
+
 ### **Unit Tests Added or Updated** (Yes / No)  
 _Indicate whether unit tests were added or modified to reflect these changes._
 
@@ -29,8 +46,28 @@ _List all other tests performed (manual or automated, including integration, reg
 
 ---
 
-### **Documentation Changes Required** (Yes / No)  
-_Indicate whether related documentation needs to be updated._
+### **Logging Added/Updated** (Yes/No)
+- Appropriate log statements are added with meaningful messages. 
+- Logging does not expose sensitive data. 
+- Log levels are used correctly (e.g., info, warn, error). 
+
+--- 
+
+### **Telemetry Added/Updated** (Yes/No) 
+- Custom telemetry (e.g., counters, timers, error tracking) is added as needed. 
+- Events are tagged with proper metadata for filtering and analysis. 
+- Telemetry is validated in staging or test environments.
+
+---
+
+### **Rollback Scenario and Process** (Yes/No)
+- Rollback plan is documented. 
+
+---
+
+### **Dependency Impact Assessed and Regression Tested** (Yes/No)
+- All impacted internal modules, APIs, services, and third-party libraries are analyzed. 
+- Results are reviewed and confirmed to not break existing functionality.
 
 ---