kubeadm: remove redundant CriticalAddonsOnly toleration from kube-proxy DaemonSet

[SataQiu]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

kubeadm: remove redundant CriticalAddonsOnly toleration from kube-proxy DaemonSet.
Given that we have used - operator: Exists, it should cover CriticalAddonsOnly. #65931 (comment)
And I do not find that kubelet and scheduler have done anything special for CriticalAddonsOnly toleration.
My test result shows that kube-Proxy can be properly scheduled to all nodes even if CriticalAddonsOnly toleration is removed.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

kubeadm: the `CriticalAddonsOnly` toleration has been removed from `kube-proxy` DaemonSet

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: SataQiu

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:

• cmd/kubeadm/OWNERS [SataQiu]

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

[neolit123]

Given that we have used - operator: Exists, it should cover CriticalAddonsOnly

i guess this is true. the old PR should have removed the CriticalAddonsOnly toleration.

also, CriticalAddonsOnly seems to be an artifact of the old addon manager under /cluster:
https://github.com/kubernetes/kubernetes/search?p=1&q=CriticalAddonsOnly
and i don't think such a taint is actively used anymore.

/lgtm
/triage accepted
/priority backlog

[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.