Remove required_status_checks for make, for now

[SgtCoDFish]

These required_status_checks apply for every branch, which breaks
backports when the job cannot run and succeed. Since the make flow
wasn't available on older branches it cannot pass on those branches.

We remove them for now until the required_status_checks are made
specific to branches where they can succeed. We'll have the opposite
problem to this down the road - we'll want to remove the bazel checks,
but release-1.9 probably won't have bazel.

[irbekrm]

/lgtm
/approve

[jetstack-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: irbekrm, SgtCoDFish

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:

• OWNERS [SgtCoDFish,irbekrm]

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

[jetstack-bot]

@SgtCoDFish: Updated the config configmap in namespace default at cluster default using the following files:

• key config.yaml using file config/config.yaml

In response to this:

These required_status_checks apply for every branch, which breaks
backports when the job cannot run and succeed. Since the make flow
wasn't available on older branches it cannot pass on those branches.

We remove them for now until the required_status_checks are made
specific to branches where they can succeed. We'll have the opposite
problem to this down the road - we'll want to remove the bazel checks,
but release-1.9 probably won't have bazel.

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.

[irbekrm]

If we implement #653 then these can be enabled again