Move periodic-kubernetes-bazel-build jobs to release-informing

[spiffxp]

Part of #18549

The intent here is to remove these jobs from the list of release-blocking jobs that need to be migrated over.

Given kubernetes/enhancements#2420 I think we should stop considering these as release-blocking, since we already have release-blocking non-bazel build jobs

[spiffxp]

/cc @ameukam @justaugustus @hasheddan
/hold
for comment from @kubernetes/release-engineering

[hasheddan]

/lgtm

[justaugustus]

/lgtm
/approve
/hold cancel

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hasheddan, justaugustus, 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/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]

@spiffxp: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

• key 1.18.yaml using file config/jobs/kubernetes/sig-release/release-branch-jobs/1.18.yaml
• key 1.19.yaml using file config/jobs/kubernetes/sig-release/release-branch-jobs/1.19.yaml
• key 1.20.yaml using file config/jobs/kubernetes/sig-release/release-branch-jobs/1.20.yaml
• key bazel-build-test.yaml using file config/jobs/kubernetes/sig-testing/bazel-build-test.yaml

In response to this:

Part of #18549

The intent here is to remove these jobs from the list of release-blocking jobs that need to be migrated over.

Given kubernetes/enhancements#2420 I think we should stop considering these as release-blocking, since we already have release-blocking non-bazel build jobs

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.