Bump kube-rbac-proxy

[oshoval]

What this PR does / why we need it:
Includes openshift/kube-rbac-proxy#80

Special notes for your reviewer:

Release note:

None

[oshoval]

/cc @RamLavi

[oshoval]

I wonder if we want hash or version
hash is static but might be deleted (we are using hash on CNAO fwiw)
version is dynamic, not deleted by might present flakes.

[RamLavi]

Can you please update the commit desc? Or is it a WIP PR that is only meant to confirm CNAO?

[oshoval]

Done, not a WIP anymore, just forgot to update
it is not dependent on CNAO, and not vice versa
CNAO just replace whatever it is to what CNAO wants

[oshoval]

Interesting here
https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/k8snetworkplumbingwg_kubemacpool/404/pull-kubemacpool-e2e-k8s/1723649479040569344

I dont think it is related to the PR
kube-rbac-proxy is a side car container that listens to the http metrics port and convert it to https,
protected by rbac

btw few days ago there was also this one (on other PR) in this area more or less

https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_cluster-network-addons-operator/1678/pull-e2e-cnao-kubemacpool-functests-release-0.89/1721495335496323072

If you want i can open issue for those 2

[oshoval]

/retest

not related to this PR imo

[qinqon]

/lgtm
/approve

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qinqon

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 [qinqon]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment