docs(github): enhance PR template for automated release notes

- Add emoji-based type categorization (feat, fix, docs, chore, etc.)
- Include 'Release Notes Impact' section to distinguish user-facing changes
- Add dedicated section for breaking changes and migration guidance
- Improve conventional commit format guidance
- Support better automated categorization in release notes generation

Author: BhaskarKulshrestha

.github/pull_request_template.md

@@ -2,13 +2,21 @@
 Explain the change in 1–3 sentences. Reference any related issues (e.g. Closes #123).
 
 ## Type of Change
-- [ ] Feature
-- [ ] Bug fix
-- [ ] Chore / Refactor
-- [ ] Docs
-- [ ] Tests
-- [ ] CI / Build
-- [ ] Other
+<!-- Select the primary type of change. This helps with automated release note generation. -->
+- [ ] 🚀 **Feature** (`feat:`) - New functionality for users
+- [ ] 🐛 **Bug fix** (`fix:`) - Fixes an issue for users
+- [ ] ⚠️ **Breaking Change** (`feat!:` or `fix!:`) - Changes that break backward compatibility
+- [ ] 📚 **Docs** (`docs:`) - Documentation updates only
+- [ ] 🔧 **Chore / Refactor** (`chore:`, `refactor:`) - Internal changes, no user impact
+- [ ] 🧪 **Tests** (`test:`) - Test additions or updates
+- [ ] 🚀 **CI / Build** (`ci:`) - Build system or CI changes
+- [ ] 📦 **Dependencies** (`deps:`) - Dependency updates
+- [ ] 🎉 **Other** - Changes that don't fit the above categories
+
+## Release Notes Impact
+<!-- This helps generate better automated release notes -->
+- [ ] **User-facing change** - Should be included in release notes
+- [ ] **Internal change only** - No need to include in release notes
 
 ## Motivation / Context
 Why is this change needed? What problem does it solve or what capability does it add?
@@ -42,12 +50,21 @@ node bin/index.js demo --services node --no-install --yes
 ```
 Result: ✅ / ❌
 
+## Breaking Changes & Migration
+<!-- If this is a breaking change, provide details for users -->
+**Breaking changes:**
+
+**Migration steps:**
+
+**Configuration changes needed:**
+
 ## Screenshots / Logs (Optional)
 Add any helpful output (chalk-styled CLI messages, error reproduction, etc.).
 
 ## Docs
 - [ ] Updated `README.md` if needed
 - [ ] Updated `.github/copilot-instructions.md` if internal conventions changed
+- [ ] Added/updated relevant documentation for user-facing changes
 - [ ] Not applicable
 
 ## Checklist