Collector pod deployed by the cluster-logging operator is using 1.3 cores of cpu on SNO DUs

cluster-logging.v5.7.5

Tested on:
4.13.4
4.14.0-ec.4
4.14.0-0.ci-2023-09-05-120503

1. Configure SNO with DU profile. 
2. Deploy cluster-logging operator and configure clusterLogging.yaml and clusterLogForwarding.yaml
3. Deploy Telco workloads and gather resource usage metrics

CPU usage is high on all three releases. There is also an increase of ~0.58 cores between 4.14.0-0.ci-2023-09-05-120503 and 4.13.4. 

clusterLogging.yaml
---
apiVersion: logging.openshift.io/v1
kind: ClusterLogging
metadata:
  name: instance
  namespace: openshift-logging
spec:
  managementState: "Managed"
  curation:
    type: "curator"
    curator:
      schedule: "30 3 * * *"
  collection:
    logs:
      type: "vector"
      vector: {}

clusterLogForwarder.yaml
---
apiVersion: "logging.openshift.io/v1"
kind: ClusterLogForwarder
metadata:
  name: instance
  namespace: openshift-logging
spec:
  outputs:
    - type: "kafka"
      name: kafka-open
      url: tcp://e28-h29-r750.alias.bos.scalelab.redhat.com:9092/e28-h37-r750
  pipelines:
    - name: audit-logs
      inputRefs:
       - audit
      outputRefs:
       - kafka-open
    - name: infrastructure-logs
      inputRefs:
       - infrastructure
      outputRefs:
       - kafka-open