add template indication to back port; create action based on label to backport changes

Author: acosferreira

.github/pull_request_template.md

@@ -11,6 +11,45 @@ Jira Issue: <https://issues.redhat.com/browse/AAP-NNNN>
 1. Pull down the PR
 2. ...
 3. ...
+## Type of Change
+- [ ] Bug fix (non-breaking change fixing an issue)
+- [ ] New feature (non-breaking change adding functionality)
+- [ ] Breaking change (fix or feature causing existing functionality to break)
+- [ ] Security fix
+- [ ] Performance improvement
+- [ ] Code refactoring
+- [ ] Documentation update
+- [ ] CI/CD update
+
+## Backport Policy
+
+This change should be:
+- [ ] **Not backported** - main/master only
+- [ ] **Backported** to specific releases (add labels after merge)
+
+### Automated Backport Instructions
+
+**After this PR is merged**, add one or more labels to automatically create backport PRs:
+
+- `backport/stable-2.4` - Backport to stable-2.4 branch
+- `backport/stable-2.5` - Backport to stable-2.5 branch
+- `backport/stable-2.6` - Backport to stable-2.6 branch
+- `backport/all` - Backport to all active stable branches
+- `no-backport` - Explicitly mark as not needing backport
+
+### Backport Justification
+<!-- Required if backporting. Explain why this needs to be in older releases -->
+<!-- Examples: -->
+<!-- - Critical bug affecting production -->
+<!-- - Security vulnerability fix (include CVE if applicable) -->
+<!-- - Regression introduced in X.Y.Z -->
+<!-- - Customer-blocking issue -->
+<!-- - Data corruption/loss prevention -->
+
+**Special backport considerations:**
+<!-- Any conflicts, dependencies, or modifications needed for backport -->
+<!-- Will this apply cleanly to older releases? -->
+<!-- Does this depend on other commits that also need backporting? -->
 
 ### Scenarios tested
 <!-- Describe the scenarios you've already manually verified, if applicable. -->