During the bonfire cicd build script, the image is tagged with a short SHA - during pr_check contexts, this is a merge commit from the source to target branch for the PR.

This makes it a bit opaque what image on quay.io is the latest for the PR HEAD commit, as the SHA doesn't match what is visible to the contributor.  This information is also relevant to IQE in trying to write and run new tests covering the PR content.

I raised this in chat and got a response from bsquizza@redhat.com with some suggestions and ideas for how to approach this.  These should be further discussed to get some consensus on what the best way to make it easier for a contributor and IQE to correctly identify a pr_check image. 

Early Proposals

1. Use the JJB plugin properties to set the GH PR check text/status/details, extending the base template to include the IMAGE_TAG in what's reported to GH.
   1. https://gitlab.cee.redhat.com/service/app-interface/-/blob/master/resources/jenkins/insights/global/base-templates.yaml#L22
2. Update the IMAGE_TAG used in bonfire's build.sh script, used by most pr_check scripts.
   1. continue to use merge commit SHA, add suffix to identify `pr-###-latest`
   2. Use PR HEAD commit SHA

These could be done in tandem, providing a consistent image tag for a given PR (pr-###-latest) and text or a direct link to the image hosted on quay.