test: pull from dockerhub

[j-zimnowoda]

📌 Summary

During code development we frequently change the code and overwrite the image tag. Unfortunately ORCS mirror cache TTL is 30 minutes, so developers get confused about the version of code that is currently running in dev cluster.

🔍 Reviewer Notes

• enforce using docker.io registry for apl dev artifacts by adding _rawValues to all deployment scenarios that are deployed via GH Actions
• removed the registry property from apl-console and apl- api to adhere to standard of using repository and tag only
• removing the job.gotmpl file

Verification

# kubectl get deployments -A -o jsonpath='{range .items[*]}{.metadata.namespace}{"/"}{.metadata.name}{" => "}{range .spec.template.spec.containers[*]}{.image}{" "}{end}{"\n"}{end}' | grep docker.io

apl-gitea-operator/apl-gitea-operator => docker.io/linode/apl-tasks:main
apl-harbor-operator/apl-harbor-operator => docker.io/linode/apl-tasks:main
apl-keycloak-operator/apl-keycloak-operator => docker.io/linode/apl-tasks:main
apl-operator/apl-operator => docker.io/linode/apl-core:APL-1279
otomi-operator/otomi-operator => docker.io/linode/apl-tasks:main
otomi/otomi-api => docker.io/linode/apl-api:main docker.io/linode/apl-core:main
otomi/otomi-console => docker.io/linode/apl-console:main

🧹 Checklist

• Code is readable, maintainable, and robust.
• Unit tests added/updated

[ElderMatt]

Tested on cluster and works.

[Ani1357]

Tested deploying cluster from github actions and confirmed desired image sources