fix image registry push issue by always pushing to whatever repo registry the pipeline runs from

Issue: Gitlab dependency bot cannot push dev image fro... (#1 - closed)

What does this MR do and why?

Our current workflow of releasing new workspace tools injector images is blocked because we are unable to push dev/test images to this repo from renovate-bot fork repos. This unblocks this by always pushing images to the container registry of the current project of the MR.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

How to set up and validate locally

Run:

OS=linux PLATFORM=amd64 ENV=local make docker-build-and-publish

to get a local build

I also validated the changes by opening an MR in the fork repo with my changes and checked pipeline successes: Test images pushed to fork repo (gitlab-org/remote-development/gitlab-workspaces-tools!11 - closed)