Update proxy release pipeline following Spinnaker 1.13 release

The image name in the manifest needs to be the same as the name that Spinnaker trigger catches. With the new release, Spinnaker now correctly recognizes gcr.io/${PROJECT_ID}/proxy as the image name.

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=244845037

java/google/registry/proxy/kubernetes/proxy-deployment-alpha.yaml

@@ -17,7 +17,7 @@ spec:
     spec:
       containers:
       - name: proxy
-        image: gcr.io/GCP_PROJECT/proxy:latest
+        image: gcr.io/GCP_PROJECT/proxy
         ports:
         - containerPort: 30000
           name: health-check

java/google/registry/proxy/kubernetes/proxy-deployment-crash-canary.yaml

@@ -17,7 +17,7 @@ spec:
     spec:
       containers:
       - name: proxy-canary
-        image: gcr.io/GCP_PROJECT/proxy:latest
+        image: gcr.io/GCP_PROJECT/proxy
         ports:
         - containerPort: 30000
           name: health-check

java/google/registry/proxy/kubernetes/proxy-deployment-crash.yaml

@@ -17,7 +17,7 @@ spec:
     spec:
       containers:
       - name: proxy
-        image: gcr.io/GCP_PROJECT/proxy:latest
+        image: gcr.io/GCP_PROJECT/proxy
         ports:
         - containerPort: 30000
           name: health-check

java/google/registry/proxy/kubernetes/proxy-deployment-production-canary.yaml

@@ -17,7 +17,7 @@ spec:
     spec:
       containers:
       - name: proxy-canary
-        image: gcr.io/GCP_PROJECT/proxy:latest
+        image: gcr.io/GCP_PROJECT/proxy
         ports:
         - containerPort: 30000
           name: health-check

java/google/registry/proxy/kubernetes/proxy-deployment-production.yaml

@@ -17,7 +17,7 @@ spec:
     spec:
       containers:
       - name: proxy
-        image: gcr.io/GCP_PROJECT/proxy:latest
+        image: gcr.io/GCP_PROJECT/proxy
         ports:
         - containerPort: 30000
           name: health-check

java/google/registry/proxy/kubernetes/proxy-deployment-sandbox-canary.yaml

@@ -17,7 +17,7 @@ spec:
     spec:
       containers:
       - name: proxy-canary
-        image: gcr.io/GCP_PROJECT/proxy:latest
+        image: gcr.io/GCP_PROJECT/proxy
         ports:
         - containerPort: 30000
           name: health-check

java/google/registry/proxy/kubernetes/proxy-deployment-sandbox.yaml

@@ -17,7 +17,7 @@ spec:
     spec:
       containers:
       - name: proxy
-        image: gcr.io/GCP_PROJECT/proxy:latest
+        image: gcr.io/GCP_PROJECT/proxy
         ports:
         - containerPort: 30000
           name: health-check

release/cloudbuild-proxy.yaml

@@ -40,13 +40,6 @@ steps:
 - name: 'gcr.io/${PROJECT_ID}/builder:latest'
   entrypoint: /bin/bash
   args: ['-c', 'mv java/google/registry/proxy/kubernetes/* .']
-# Replace the tag "latest" with the git tag that triggered this build. This is due to a bug in
-# Spinnaker where the tag is appended to the image name when the deployment pipeline is triggered
-# by GCB pubsub messages. The bug is fixed in https://github.com/spinnaker/echo/pull/498 and we can
-# remove this step and the "latest" tag in the manifests when Spinnaker 1.13 is deployed.
-- name: 'gcr.io/${PROJECT_ID}/builder:latest'
-  entrypoint: /bin/bash
-  args: ['-c', 'sed -i s/:latest/:${TAG_NAME}/ proxy-*.yaml']
 # Push the image. We can't let Cloud Build's default processing do that for us
 # because we need to push the image before we can sign it in the following
 # step.