chore: build and push "directly" instead of using mozilla-it/deploy-actions

[chenba]

We relied on mozilla-it/deploy-actions's build-and-push to push a couple of Docker images to another GAR in GCP. That duplicate the image builds. With this patch we'll define the build-and-push actions ourselves.

Additionally, we'll push a 'latest' tag to the non-enterprise image registries on a git tag push.

Closes STOR-499, STOR-509

[pjenvey]

I'll just note the obvious that we could go even further, breaking apart our usage of the build action (I noticed remote-settings basically rolls their own https://github.com/mozilla/remote-settings/blob/main/.github/workflows/publish-ent.yaml) or even tweaking the mozcloud actions/workflow to better suite these needs

But this is definitely a good, easy improvement

[pjenvey]

I notice the mozcloud docker-push action does a docker/login-action here instead: https://github.com/mozilla-it/deploy-actions/blob/b9d76236c1d1dd89daab4ea15651cbe76574267a/docker-push/action.yml#L39 I'm not sure it matters?

[taddes]

Yeah, this would be good to update since I was planning on breaking those out in the broader workflow updates.

[chenba]

(I noticed remote-settings basically rolls their own https://github.com/mozilla/remote-settings/blob/main/.github/workflows/publish-ent.yaml)

Thanks, I'll take a look.

[chenba]

The two GAR pushes are on different steps; it appears docker/login-action won't allow two auth sessions to us-docker.pkg.dev simultaneously. Not a big deal since the later step can rely on cache.

[pjenvey]

This evolved into more of a setup-build-and-push action, I think it could use a renaming to something along those lines?

[chenba]

✅

[mozcloud-preview-environments]

Preview environment has been deployed.

Preview URL: https://pr2149-tokenserver.preview.mozilla.cloud

It may take up to 5 minutes for the environment to become available.
If the link doesn't work immediately, please wait a few moments and try again.

You can monitor deployment status in Argo CD.