[JIRA] (OVIRT-1717) When a component build passes OST, tag its git hash

When a component build passes OST, tag its git hash --------------------------------------------------- Key: OVIRT-1717 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1717 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Change Queue Reporter: danken Assignee: Daniel Belenky Labels: change-queue, standard-ci As a project maintainer, I want to see which changes passed CI gating (aka CQ) so that it will be easy for me to tell if a specific commit was tested in CQ and is available for QA. *Scenario:* Project maintainer specifies in _stdci.yaml_ config that he wants STDCI to tag changes of this project by specifying {code:java} tag-on-release: enabled: True tag_template: "SomeTemplate with Jinja support { branch } and { queue_name } variables should be available too" {code} "standard stage" will add the relevant information to the change object and CQ will handle the tagging. Need to see if the tags will be pushed by CQ as well or another component should be used (such as pusher.py)