removes canary job that tested migration changes

[RobertKielty]

fixes #18854

The configuration changes were ...

migrating pull-kubernetes-e2e-gce-network-proxy-http-connect
onto the k8s-infra-prow-build cluster

removing container startup flag --gcp-project=k8s-network-proxy-e2e

@spiffxp
This is a second PR to implement this change I closed the previous one.

The presentation of the diff here by git is awkward owing to the duplication of the job to canary test the changes.

[spiffxp]

needs rebase, I will check on in this tomorrow AM PT

[spiffxp]

/approve
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: RobertKielty, spiffxp

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• config/jobs/kubernetes/sig-api-machinery/OWNERS [spiffxp]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

@RobertKielty: Updated the job-config configmap in namespace default at cluster default using the following files:

• key sig-api-machinery-config.yaml using file config/jobs/kubernetes/sig-api-machinery/sig-api-machinery-config.yaml

In response to this:

fixes #18854

The configuration changes were ...

migrating pull-kubernetes-e2e-gce-network-proxy-http-connect
onto the k8s-infra-prow-build cluster

removing container startup flag --gcp-project=k8s-network-proxy-e2e

@spiffxp
This is a second PR to implement this change I closed the previous one.

The presentation of the diff here by git is awkward owing to the duplication of the job to canary test the changes.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.