[release-1.12] Remove deprecated kubelet credential provider flag

[k8s-infra-cherrypick-robot]

This is an automated cherry-pick of #4436

/assign CecileRobertMichon

Remove deprecated kubelet credential provider flag

[nojnhuh]

/lgtm
/approve

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 2bca822a9a276113aff6b313beea6a6c94781f33

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nojnhuh

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

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (97720be) 59.76% compared to head (cce46c8) 59.76%.
Report is 1 commits behind head on release-1.12.

Additional details and impacted files

@@              Coverage Diff              @@
##           release-1.12    #4437   +/-   ##
=============================================
  Coverage         59.76%   59.76%           
=============================================
  Files               192      192           
  Lines             19316    19316           
=============================================
  Hits              11544    11544           
  Misses             7143     7143           
  Partials            629      629           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[nojnhuh]

Upgrade test failure is the same as #4422:

/override pull-cluster-api-provider-azure-apiversion-upgrade-v1beta1

[k8s-ci-robot]

@nojnhuh: Overrode contexts on behalf of nojnhuh: pull-cluster-api-provider-azure-apiversion-upgrade-v1beta1

In response to this:

Upgrade test failure is the same as #4422:

/override pull-cluster-api-provider-azure-apiversion-upgrade-v1beta1

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.