Improve release scripts to automate missing steps

According to the conversation on the dev mailing list one pain point of the release making is that even with the latest create-release script a lot of steps are not automated.

This Jira is about creating a script which guides the release manager throw the proces:

Goals:

• It would work even without the apache infrastructure: with custom configuration (forked repositories/alternative nexus), it would be possible to test the scripts even by a non-commiter.
• every step which could be automated should be scripted (create git branches, build,...). if something could be not automated there an explanation could be printed out, and wait for confirmation
• Before dangerous steps (eg. bulk jira update) we can ask for confirmation and explain the
• The run should be idempontent (and there should be an option to continue the release from any steps).