Description of problem:
Logging 5.4 is utilizing cronjobs.v1beta1.batch which is deprecated and will be removed in Kube 1.25 and thus OpenShift 4.12. Clusters which have components which hit deprecated APIs which will be removed in the next release or next EUS release generate warning level alerts so that the admin knows that they've got something which must be addressed before upgrading to the next or next EUS release. Therefore we should ensure that all components which can be installed in 4.10 no longer utilized these deprecated APIs.

Version-Release number of selected component (if applicable):
cluster-logging.5.4.1-24

How reproducible:
100%

Steps to Reproduce:
1. Install 4.10.12+
2. Install logging 5.4
3. Observe APIRemovedInNextEUSReleaseInUse and retrieve apirequest counts on the cronjob api.

Actual results:
$ oc get apirequestcounts cronjobs.v1beta1.batch -o jsonpath='

{","}

{","} {.userAgent} {"\n"} {end}' | sort -k 2 -t, -u | column -t -s, -NVERBS,USERNAME,USERAGENT
VERBS USERNAME USERAGENT
delete system:serviceaccount:openshift-logging:cluster-logging-operator cluster-logging-operator/v0.0.0

Expected results:
No use of deprecated APIs which will be removed in OCP 4.12.

Additional info:
Please see https://access.redhat.com/articles/6955381 which documents removals in 4.12

Also upstream docs https://github.com/kubernetes/website/blob/main/content/en/docs/reference/using-api/deprecation-guide.md
It'd be great to remove all deprecated API use for the next several releases if possible.