Operator: Configure kube-rbac-proxy sidecar to use Intermediate TLS security profile in OCP

[aminesnow]

What this PR does / why we need it:
This PR adds Intermediate security profile to the kube-rbac-proxy operator sidecar.

Checklist

• Documentation added
• Tests updated
• Is this an important fix or new feature? Add an entry in the CHANGELOG.md.
• Changes that require user attention or interaction to upgrade are documented in docs/sources/upgrading/_index.md

[grafanabot]

./tools/diff_coverage.sh ../loki-main/test_results.txt test_results.txt ingester,distributor,querier,querier/queryrange,iter,storage,chunkenc,logql,loki

Change in test coverage per package. Green indicates 0 or positive change, red indicates that test coverage for a package fell.

+           ingester	0%
+        distributor	0%
+            querier	0%
+ querier/queryrange	0%
+               iter	0%
+            storage	0%
+           chunkenc	0%
+              logql	0%
+               loki	0%

[alanconway]

I don't think this implements https://issues.redhat.com/browse/OCPPLAN-4379
which says: "Goal: Cluster-wide TLS configuration"
I believe the goal is to use the same TLS profile as the apiserver/cluster object by default, not to hard-code a set of cipher suites. The cluster admin is supposed to be able to configure the desired cluster-wide default by modifying apiserver.spec.tlsSecurityProfile

oc get apiserver/cluster -o template='{{.spec.tlsSecurityProfile}}'

[periklis]

@alanconway I believe you grabbed to wrong PR. You are probably looking for #6870 that implements what you are saying for our gateway. A pending PR for Loki is in progress by @Red-GV