promoting images with go191

[longwuyuan]

• Built new images because of bump go to v1.19.1 ingress-nginx#9057
• Lot of related info is here as well Vulnerability CVE-2022-30580 ingress-nginx#8932
• This PR promotes the new images that now contain go v1.19.1
• This PR makes a significant promotion in the test-runner image because that sha has to be updated in the ingress-nginx project's main, for the ingres-nginx-controller's binary to get compiled with go v1.19.1. Reason being the build system uses a docker environ to compile the binary and the docker-environ is built using the test-runner image being promoted here
• Also changing convention on the tagging for kube-webhook-certgen image and the nginx-errors image because the current tagging convention is not really based on any pre-requisite. So now changed tagging to the registry provided tag that includes a date & some id

/tirage accepted

/assign @tao12345666333 @strongjz @rikatz

[strongjz]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: longwuyuan, strongjz

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:

• k8s.gcr.io/images/k8s-staging-ingress-nginx/OWNERS [strongjz]

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

[longwuyuan]

/check-cla

[strongjz]

/check-cla

[k8s-triage-robot]

Unknown CLA label state. Rechecking for CLA labels.

Send feedback to sig-contributor-experience at kubernetes/community.

/check-cla
/easycla