gitlab-runner-helper IronBank image has gitlab-runner-* binaries in wrong location
Bug
Description
I deployed Gitlab (https://repo1.dso.mil/platform-one/big-bang/apps/developer-tools/gitlab/-/blob/4.8.0-bb.0) and Gitlab-runner (https://repo1.dso.mil/platform-one/big-bang/apps/developer-tools/gitlab-runner/-/blob/0.19.2-bb.2) as part of the BigBang flux stack. I'm working off the jaic-ocp branch, which has changes for some apps specific to OpenShift (none for Gitlab) but otherwise mirrors master. This should be merged soon.
When testing a pipeline that attempts to upload or download artifacts, I receive the following error stating that the gitlab-runner-helper binary cannot be located.
The same thing happens on attempted artifact download.
To investigate this, I exec'd onto the gitlab-runner-helper container inside the temporary runner pod and confirmed that the expected file is in /usr/local/bin instead of /usr/bin
I manually copied this binary to /usr/bin within this container and the job was able upload artifacts as expected. I looked through the helm charts for gitlab-runner but was unable to find any way to modify this behavior there.