Annotate deprecated functions to allow linters to catch usage

[rbjorklin]

It would be useful to have linters assist in discovering use of deprecated api versions before they are eventually removed from client-go.

For example PDBs graduated to policy/v1 in k8s 1.21 and were eventually removed in k8s 1.25. Assuming I have linters configured correctly it would be helpful to get notified of these changes prior to the old version being removed or intentionally going looking for the information.

// Deprecated: use V1().PodDisruptionBudgets() instead. Since: v0.21.0

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale