releng: Use a temp namespace for k8s-staging-kubernetes promotion

As the k8s.gcr.io VDF (Vanity Domain Flip) hasn't occured yet, Release
Managers should use the releng-vdf-temp-prod namespace to test image
promotion for production official k8s.gcr.io container images.

Signed-off-by: Stephen Augustus <saugustus@vmware.com>

k8s.gcr.io/manifests/k8s-staging-kubernetes/promoter-manifest.yaml

@@ -15,9 +15,11 @@
 registries:
 - name: gcr.io/k8s-staging-kubernetes
   src: true
-- name: us.gcr.io/k8s-artifacts-prod
+# TODO(justaugustus): Change these values to {us,eu,asia}.gcr.io/k8s-artifacts-prod (ROOT level)
+#                     after releng image promotion testing is complete AND BEFORE the vanity domain flip.
+- name: us.gcr.io/k8s-artifacts-prod/releng-vdf-temp-prod
   service-account: k8s-infra-gcr-promoter@k8s-artifacts-prod.iam.gserviceaccount.com
-- name: eu.gcr.io/k8s-artifacts-prod
+- name: eu.gcr.io/k8s-artifacts-prod/releng-vdf-temp-prod
   service-account: k8s-infra-gcr-promoter@k8s-artifacts-prod.iam.gserviceaccount.com
-- name: asia.gcr.io/k8s-artifacts-prod
+- name: asia.gcr.io/k8s-artifacts-prod/releng-vdf-temp-prod
   service-account: k8s-infra-gcr-promoter@k8s-artifacts-prod.iam.gserviceaccount.com