Add Release Pull Request template with semantic title guidelines

- Introduced a dedicated Pull Request template for release preparation under `.github/.github/PULL_REQUEST_TEMPLATE/Release.md`.
- Defined detailed guidelines for PR title formatting, including allowed types (e.g., security, fix, perf) and scopes (e.g., application, domain, infrastructure).
- Provided a checklist for key release tasks, such as updating CHANGELOG, running tests, and confirming CI/CD pipeline success.
- Added sections for version details, related branches, and special release instructions to streamline the release process.
- Supports adherence to semantic and standardized contribution practices.

Author: dieselxxx

.github/PULL_REQUEST_TEMPLATE/Release.md

@@ -0,0 +1,56 @@
+# 🔖 Release PR
+
+<!--
+PR TITLE FORMAT (REQUIRED):
+
+<type>(<scope>): <short imperative summary>
+
+Allowed types:
+- security
+- fix
+- perf
+- feat
+- refactor
+- docs
+- chore
+- ci
+- composer
+
+Allowed scopes:
+application | domain | infrastructure | kernel | shared | support | tests | deps | other
+
+PR semantic MUST represent the DOMINANT change.
+Priority order:
+security > fix > perf > feat > refactor > docs > chore > ci > composer
+-->
+
+### Version
+
+- Release version: `vX.Y.Z`
+
+### Related Branches
+
+- Release branch: `release/vX.Y.Z`
+- Target branch: `develop` / `master` (delete as appropriate)
+
+### Description
+
+This PR prepares the release branch for version `vX.Y.Z`. It should include:
+
+- Changelog updates
+- README / documentation updates
+- Any configuration changes required for release
+- Final fixes / tweaks
+
+### Checklist
+
+- [ ] Update `CHANGELOG.md` for this release
+- [ ] Update `README.md` if needed
+- [ ] Run tests for all core and adapter modules
+- [ ] Verify CI/CD pipelines pass
+- [ ] Tag release commit with version `vX.Y.Z`
+- [ ] Merge release branch into `develop` \ `master`
+
+### Notes / Special Instructions
+
+- Include any special notes about the release, deployment instructions, or known issues.