Change kube rbac proxy's default log level to zero and make it configurable

[skonto]

Fixes JIRA #

Proposed Changes

• Fixes #2740, similar issue to https://github.com/kubernetes-sigs/kubebuilder/issues/2434.
• User can inject the desired log level at the corresponding operator CR as follows:

  spec:
  config:
  logging:
    loglevel.kube-rbac-proxy: "10"

[matzew]

@skonto this is for all three CRs? KnativeServing, KnativeEventing and our custom KnativeKafka ?

[matzew]

/retest

[skonto]

this is for all three CRs?

It should be as InjectRbacProxyContainer is called from these components.

[pierDipi]

/lgtm /approve

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pierDipi, skonto

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

The pull request process is described here

Needs approval from an approver in each of these files: - ~~[OWNERS](https://github.com/openshift-knative/serverless-operator/blob/main/OWNERS)~~ [pierDipi,skonto] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[pierDipi]

/cherry-pick release-1.33

[pierDipi]

/cherry-pick release-1.32

[openshift-cherrypick-robot]

@pierDipi: once the present PR merges, I will cherry-pick it on top of release-1.33 in a new PR and assign it to you.

In response to [this](https://github.com/openshift-knative/serverless-operator/pull/2749#issuecomment-2209264954): >/cherry-pick release-1.33 Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

[openshift-cherrypick-robot]

@pierDipi: once the present PR merges, I will cherry-pick it on top of release-1.32 in a new PR and assign it to you.

In response to [this](https://github.com/openshift-knative/serverless-operator/pull/2749#issuecomment-2209264997): >/cherry-pick release-1.32 Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

[openshift-cherrypick-robot]

@pierDipi: new pull request created: #2756

In response to [this](https://github.com/openshift-knative/serverless-operator/pull/2749#issuecomment-2209264954): >/cherry-pick release-1.33 Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

[openshift-cherrypick-robot]

@pierDipi: new pull request created: #2757

In response to [this](https://github.com/openshift-knative/serverless-operator/pull/2749#issuecomment-2209264997): >/cherry-pick release-1.32 Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.