ack-route53resolver-controller missing from operatorhub catalogsource in OpenShift 4.16

[mumlawski]

Describe the bug
We do subscribe all our ack controllers to operatorhub CatalogSources. We have noticed that ack-route53resolver-controller is now missing in this catalogsource and we had to switch to community operators to continue using latest controller versions.

Steps to reproduce

oc get packagemanifests -n openshift-marketplace | grep route53
ack-route53-controller                                OperatorHub.io        471d
ack-route53-controller                                Community Operators   471d
ack-route53resolver-controller                        Community Operators   471d

oc logs -n openshift-operator-lifecycle-manager catalog-operator
I0224 07:30:17.166649       1 event.go:298] Event(v1.ObjectReference{Kind:"Namespace", Namespace:"", Name:"ack-system", UID:"fcb4b6fd-f4a5-48c4-ae80-84042035de71", APIVersion:"v1", ResourceVersion:"71638071", FieldPath:""}): type: 'Warning' reason: 'ResolutionFailed' constraints not satisfiable: subscription ack-route53resolver-controller exists, no operators found in package ack-route53resolver-controller in the catalog referenced by subscription ack-route53resolver-controller

Expected outcome
We want to understand to which CatalogSources we should subscribe going forward for our controllers. Should we switch all our controllers to community operator catalogsource or ack-route53resolver-controller missing in operatorhub was done accidentally?

Environment
All our OpenShift 4.16.32 clusters

• Kubernetes version v1.29.11+ef2a55c
• Using EKS (yes/no), if so version? No, OpenShift
• AWS service targeted (S3, RDS, etc.) N/A