Update template generation for Freshmaker builds

Currently, we are unable to use Freshmaker builds with our test automation due to Freshmaker's image tagging scheme. When Freshmaker auto respins an image to address a base image CVE, it appends a build number hash to the end of the original image's existing Docker tag. e.g. amq7/amq-streams-operator:1.1.0 becomes amq7/amq-streams-operator:1.1.0-1.1554729677 [1]. Since the build number hash appended to each image tag varies between images of the same respin, we cannot use our existing image test automation as the automation expects an identical tag between images of the same respin. [2] This requires us to respin all our container images manually every time a CVE hits in order to ensure our images share a common tag.

The Freshmaker team is unable to supply our respun image with consistent tags [3] since the builds number hashes are used to uniquely identify the builds in brew. This means that we would need to enhance our automation to be able to handle Freshmaker builds if we wish to save ourselves from the manual respins.

This task is to investigate/implement a way for our automation to update our install/deployment files e.g. 050-Deployment-strimzi-cluster-operator.yaml[4] with Freshmaker builds.

[1] https://projects.engineering.redhat.com/browse/FACTORY-4362
[2] https://github.com/strimzi/strimzi-kafka-operator/blob/f45bcef61bee31a1eb5b7897ea15123b03bc927a/systemtest/src/main/java/io/strimzi/systemtest/utils/StUtils.java#L438-L453
[3] https://projects.engineering.redhat.com/browse/FACTORY-4787
[4] https://github.com/strimzi/strimzi-kafka-operator/blob/f45bcef61bee31a1eb5b7897ea15123b03bc927a/install/cluster-operator/050-Deployment-strimzi-cluster-operator.yaml