Use new build targets for release workflows.

[SanjayVas]

• //src/main/docker:push_all_gke_images target for push image workflow
• Kustomize-based targets for K8s workflows.

[wfa-reviewable]

This change is 

[SanjayVas]

Depends on #948

[stevenwarejones]

Reviewed 5 of 5 files at r1, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @SanjayVas)

[stevenwarejones]

Reviewed 1 of 1 files at r2, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @SanjayVas)

---

.github/workflows/configure-kingdom.yml line 110 at r2 (raw file):

        uses: google-github-actions/get-gke-credentials@v1
        with:
          cluster_name: kingdom

you want this fixed?

[SanjayVas]

Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @stevenwarejones)

---

.github/workflows/configure-kingdom.yml line 110 at r2 (raw file):

Previously, stevenwarejones (Steven Ware Jones) wrote…

you want this fixed?

It simplifies things to have the cluster names be static. We don't plan to put more than one Kingdom cluster in the QA/nightly cloud projects. I just recreated the cluster in halo-cmm-dev to match this name.

This is consistent with how we use static cluster names for the Duchies as well (worker1_duchy, worker2_duchy, aggregator_duchy).

[stevenwarejones]

Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @SanjayVas)