[MAISTRA-624] Use basic HTTP auth for internal communication

[jwendell]

Between kiali, grafana, jaeger and prometheus.

This way we can get rid of cluster role bindings.

We create an htpasswd secret unconditionally on the beginning of the control
plane installation, configure all oauth proxies to use that htpasswd
file as another form of authentication and finally configure Kiali
CR to use HTTP basic auth to communicate with those services.

[jpkrohling]

Jaeger Operator PR: jaegertracing/jaeger-operator#573

[objectiser]

@jwendell FYI - the new Jaeger images are listed here, and should hopefully be approved by our QE tomorrow.

Note that the image names have changed.

[dmitri-d]

lgtm

[jwendell]

@objectiser @jpkrohling Are you going to release a new community image with those changes in?

Currently we are installing jaeger operator using the v1.13.1 tag, which points to the image jaegertracing/jaeger-operator:1.13.1.

On my tests, using an image generated by @jpkrohling , I was only able to deploy the jaeger operator if using latest CR's from master (instead of using the v1.13.1 GitHub tag). So, I believe that just pushing a new image to docker hub under the same [floating] 1.13.1 tag is not enough.

[jpkrohling]

We have a master tag that represents the current state of master. Our plan is to release a new operator version as soon as a new Jaeger version is released, as we usually do. If there's a need in the community for an operator release before 1.14 is released, we can certainly do so.

[jwendell]

Manually merged because mergify is dead