🌱 Add back more v1beta1 util functions from v1.10.3

[pierreprinetti]

What this PR does / why we need it:

With v1beta2, some v1beta1 util functions have been saved in util/deprecated/v1beta1 for consumers that still support v1beta1 objects. This patch adds more v1beta1-focused utils packages to the deprecated/v1beta1 folder:

• util
• util/annnotations
• util/collections
• util/predicates

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #12440

[k8s-ci-robot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign justinsb for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

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

[pierreprinetti]

/area util

[k8s-ci-robot]

@pierreprinetti: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-cluster-api-test-main	b77e212	link	true	/test pull-cluster-api-test-main

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

[fabriziopandini]

@pierreprinetti what is the use case for restoring this utils?
Have you read the recommendation from first point in https://main.cluster-api.sigs.k8s.io/developer/providers/migrations/v1.10-to-v1.11#suggested-changes-for-providers (conditions utils are so far the only temporary exception to this rule, but everything else v1beta1 is going away for good reasons)

[fabriziopandini]

/close

As per kubernetes-sigs/cluster-api-provider-openstack#2611 (comment)

That is: CAPO controllers will consume CAPI v1beta2 objects, but will themselves continue to publish infra objects conforming to CAPI v1beta1. We've been set a deadline of August next year to move to v1beta2, though, so we should probably get on that.

[k8s-ci-robot]

@fabriziopandini: Closed this PR.

In response to this:

/close

As per kubernetes-sigs/cluster-api-provider-openstack#2611 (comment)

That is: CAPO controllers will consume CAPI v1beta2 objects, but will themselves continue to publish infra objects conforming to CAPI v1beta1. We've been set a deadline of August next year to move to v1beta2, though, so we should probably get on that.

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.