Hono-Release-Pipeline

• Checks out ${BRANCH}
• bumps POMs to ${RELEASE_VERSION}
• builds and tests it
• tags it with ${RELEASE_VERSION}
• bumps POMs to ${NEXT_VERSION}
• pushes POMs and newly created tag to GitHub
• publishes eclipse-hono-deploy-${RELEASE_VERSION}.tar.gz and hono-cli-${RELEASE_VERSION}-exec.jar to the download server.

NB in order to publish the artifacts to the Eclipse repository or to Maven Central you need to manually start the Deploy-Eclipse or Deploy-Maven-Central build jobs respectively after this job has completed successfully.