Automate releases with GH actions

[kwin]

Releases currently require quite some manual steps outlined at https://github.com/Adobe-Consulting-Services/acs-aem-commons/blob/master/RELEASING.md and in particual personal OSSRH credentials which need to have deploy rights for group id com.adobe.acs. Also the javadoc should be automatically uploaded to https://adobe-consulting-services.github.io/acs-aem-commons/apidocs/ (which is very outdated right now).

The release should be automated with GH actions as well and a repo secret should be used for the OSSRH deploy credentials. As repo/organization secrets are not exposed by GitHub, storing it there should be fairly safe.

That would allow to release more often, with less effort and allow more people to perform the release (everyone with write access to the repo)

Open issues:

• [ ] Which GPG private key to use for signing as required by https://central.sonatype.org/publish/requirements/gpg/?

[kwin]

Some references

• https://gist.github.com/sualeh/ae78dc16123899d7942bc38baba5203c
• https://docs.github.com/en/actions/managing-workflow-runs/manually-running-a-workflow
• https://docs.github.com/en/actions/reference/events-that-trigger-workflows#workflow_dispatch
• https://github.com/adobe/aem-core-wcm-components/blob/master/.github/workflows/maven-release.yml

[kwin]

I would suggest creating a new PGP keypair for code signing and placing it as organisation secret together with the passphrase. Alternatively it has to be placed as repository secret in both https://github.com/Adobe-Consulting-Services/acs-aem-commons/settings/secrets/actions and https://github.com/Adobe-Consulting-Services/acs-aem-tools/settings/secrets/actions. In addition a new OSSRH account which is not bound to a particular user would be good to allow to deploy to OSSRH Maven repository. Those credentials need to be available as Org/Repo secrets as well. @davidjgonzalez Can you take care of creating those, publishing the public PGP key to the necessary keyservers and create a new OSSRH account which has write access to the group id of acs-aem-commons and acs-aem-tools?