change kubectl_node_schedulable var

[rptaylor]

What type of PR is this?
/kind cleanup

What this PR does / why we need it:
If you have these nodes:

cluster-k8s-node-x39      Ready                      <none>          279d     v1.29.10
cluster-k8s-node-x40      Ready,SchedulingDisabled   <none>          279d     v1.29.10

then the results of this query are:

$ kubectl get node cluster-k8s-node-x39 -o jsonpath='{ .spec.unschedulable }'
$ kubectl get node cluster-k8s-node-x40 -o jsonpath='{ .spec.unschedulable }'
true

In other words kubectl_node_schedulable is the opposite of what it says - it is true if the node is un schedulable.

Which issue(s) this PR fixes:

Make the name of the variable match the logic of the variable to improve readability and avoid the risk of confusion and errors.

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

NONE

[k8s-ci-robot]

Hi @rptaylor. Thanks for your PR.

I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

[yankay]

/ok-to-test

[tico88612]

/retest

[tico88612]

@rptaylor, please rebase this PR

[rptaylor]

@tico88612 Okay I rebased it, can you please approve and merge before it gets out of date again?

[rptaylor]

Looks like the CI/CD is broken.

[tico88612]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rptaylor, tico88612

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 [tico88612]

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