chore: fixed discussions notification target in .asf.yaml and syncd pull request template since "squash and merge" is enabled

Author: lprimak

.asf.yaml

@@ -34,4 +34,5 @@ notifications:
   pullrequests: [email protected]
   commits: [email protected]
   issues: [email protected]
+  discussions: [email protected]
   jira_options: link label worklog

.github/pull_request_template.md

@@ -8,15 +8,14 @@ Following this checklist to help us incorporate your contribution quickly and ea
  - [ ] Make sure there is a [GitHub issue](https://github.com/apache/shiro/issues) filed
        for the change (usually before you start working on it).  Trivial changes like typos do not
        require a GitHub issue.  Your pull request should address just this issue, without pulling in other changes.
- - [ ] Each commit in the pull request should have a meaningful subject line and body.
  - [ ] Format the pull request title like `[#XXX] - Fixes bug in SessionManager`,
        where you replace `#XXX` with the appropriate GitHub issue. Best practice
        is to use the GitHub issue title in the pull request title and in the first line of the commit message.
  - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  - [ ] add `fixes #XXX` if merging the PR should close a related issue.
  - [ ] Run `mvn verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
- - [ ] If you have a group of commits related to the same change, please squash your commits into one and force push your branch using `git rebase -i`.
  - [ ] Committers: Make sure a milestone is set on the PR
+ - [ ] Committers: Use "Squash and Merge" to combine all commits into one when merging a PR when appropriate.
 
 Trivial changes like typos do not require a GitHub issue (javadoc, comments...).
 In this case, just format the pull request title like `[DOC] - Add javadoc in SessionManager`.