update rule for monitoring.coreos.com

[ChuckHend]

To resolve

2024-05-29T13:22:46.060830Z ERROR reconciling object:reconcile:reconcile: controller::app_service::manager:669: ns: reportedly-hot-falconet, failed to apply PodMonitor for AppService: reportedly-hot-falconet-embeddings, error: Kube Error: ApiError: podmonitors.monitoring.coreos.com "reportedly-hot-falconet-embeddings" is forbidden: : Forbidden (ErrorResponse { status: "Failure", message: "podmonitors.monitoring.coreos.com \"reportedly-hot-falconet-embeddings\" is forbidden: ", reason: "Forbidden", code: 403 }) object.ref=CoreDB.v1alpha1.coredb.io/reportedly-hot-falconet.reportedly-hot-falconet object.reason=object updated trace_id=00000000000000000000000000000000

[sjmiller609]

I don't think this is the right policy, normally it's like this:

items:
# first part before the slash is the API group, after the slash is the API version
- apiVersion: monitoring.coreos.com/v1
# resource name
  kind: PodMonitor
  metadata: