[SHIRO-838] fix hashes

[bmarwell]

• attach hashes for source release zip file

Checked work this time, so it is actually attached:

$ mvn verify deploy:deploy -DaltDeploymentRepository=snapshots::default::file:///$HOME/.m2/testrepo -Pdocs,apache-release 
[...]

 $ find  $HOME/.m2/testrepo -name "*.zip*"
./org/apache/shiro/shiro-root/1.9.0-SNAPSHOT/shiro-root-1.9.0-20220304.205727-1-source-release.zip
./org/apache/shiro/shiro-root/1.9.0-SNAPSHOT/shiro-root-1.9.0-20220304.205727-1-source-release.zip.sha1
./org/apache/shiro/shiro-root/1.9.0-SNAPSHOT/shiro-root-1.9.0-20220304.205727-1-source-release.zip.md5
./org/apache/shiro/shiro-root/1.9.0-SNAPSHOT/shiro-root-1.9.0-20220304.205727-1-source-release.zip.sha512
./org/apache/shiro/shiro-root/1.9.0-SNAPSHOT/shiro-root-1.9.0-20220304.205727-1-source-release.zip.sha512.sha1
./org/apache/shiro/shiro-root/1.9.0-SNAPSHOT/shiro-root-1.9.0-20220304.205727-1-source-release.zip.sha512.md5
./org/apache/shiro/shiro-root/1.9.0-SNAPSHOT/shiro-root-1.9.0-20220304.205727-1-source-release.zip.asc

The duplicate hashes are created by the deploy-plugin, which will actually always hash project artifacts.

Following this checklist to help us incorporate your contribution quickly and easily:

• Make sure there is a JIRA issue filed
  for the change (usually before you start working on it). Trivial changes like typos do not
  require a JIRA 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 [SHIRO-XXX] - Fixes bug in SessionManager,
  where you replace SHIRO-XXX with the appropriate JIRA issue. Best practice
  is to use the JIRA 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.
• Run mvn clean install apache-rat:check 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.

Trivial changes like typos do not require a JIRA issue (javadoc, comments...).
In this case, just format the pull request title like (DOC) - Add javadoc in SessionManager.

If this is your first contribution, you have to read the Contribution Guidelines

If your pull request is about ~20 lines of code you don't need to sign an Individual Contributor License Agreement
if you are unsure please ask on the developers list.

To make clear that you license your contribution under the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

• I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004
• In any other case, please file an Apache Individual Contributor License Agreement.

[bdemers]

+1 with suggestion