Add deployments and automated tagging

This revamps the non-scheduled jobs (aka those running on branches) quite a bit.

The new pipeline for those starts with a similar build stage, which now only builds. This allows it to run in far more cases, e.g. to run on topic branches to give them a minimal round of testing.

After build for the apertis branches there is a postbuild stage which runs one job that uploads the snapshot build straight away while a second job blocks on a manual trigger to do a release of the package. When that job is manually triggered the package gets signed and rebuild followed by a further job that will upload that build and does a submit-request to OBS.

Signed-off-by: Sjoerd Simons sjoerd.simons@collabora.co.uk