remove remaining deprecated taints from 1.9

[shivnagarajan]

What this PR does / why we need it:

👋 Am new here 😄

This relates to #64260

which was the previous attempt at removing the deprecated tolerations.

Since these deprecated tolerations need no longer be supported, it is better to completely remove support for them. This change completely removes all references to DeprecatedTaintNodeUnreachable and DeprecatedTaintNodeNotReady.

To remove confusion, and based on previous comments in the code, this change removes all of the handling for the deprecated tolerations altogether. This follows the deprecation policy outlined in https://kubernetes.io/docs/reference/using-api/deprecation-policy/.

Special notes for your reviewer:

Release note:

As per deprecation policy in https://kubernetes.io/docs/reference/using-api/deprecation-policy/ 
the taints "node.alpha.kubernetes.io/notReady" and "node.alpha.kubernetes.io/unreachable".  are no
longer supported or adjusted. These uses should be replaced with "node.kubernetes.io/not-ready" 
and "node.kubernetes.io/unreachable" respectively instead.

[k8s-ci-robot]

Hi @shivnagarajan. Thanks for your PR.

I'm waiting for a kubernetes 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/test-infra repository.

[shivnagarajan]

/cc @resouer @bsalamat

[xiaoxubeii]

/ok-to-test

[k82cn]

/approve for nodelifecycle and scheduler part :)

[k82cn]

/kind cleanup

[shivnagarajan]

/assign @deads2k

[shivnagarajan]

/assign @derekwaynecarr

[shivnagarajan]

ping @deads2k @derekwaynecarr

Could either of you take a quick look? You are listed as owners/approvers for

• plugin/pkg/admission/OWNERS

[yastij]

/lgtm

[yastij]

/lgtm

[yastij]

/priority backlog

[shivnagarajan]

Is there someone else available to review/approve this?

[resouer]

/lgtm

/assign @liggitt
for approve

[resouer]

/lgtm

/assign @liggitt
for approve

[k8s-ci-robot]

@resouer: GitHub didn't allow me to assign the following users: for, approve.

Note that only kubernetes members and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/lgtm

/assign @liggitt for approve

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.

[liggitt]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: k82cn, liggitt, shivnagarajan

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:

• pkg/controller/nodelifecycle/OWNERS [k82cn,liggitt]
• pkg/scheduler/OWNERS [k82cn,liggitt]
• plugin/pkg/admission/OWNERS [liggitt]

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

[fejta-bot]

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel or /hold comment for consistent failures.