Proposal: Remove certificate management from component

[mhutter]

Context

Managing the certificates for incoming traffic (for edge, passthrough and reencrypt setups) make this component unnecessarily complex. The component tries to deduct from all the input, what certificates must be created from which source and configured in which way for Keycloak itself and the Ingress object. (also see #115 and #99 #98 #96 )

I would propose to remove the whole certificate creation logic from this component, and leave it to dedicated components or the user.

In this component:

• select a TLS mode
• optionally annotate services (such as to generate OpenShift Service Serving Certs)
• configure which secret to use for certificates (igress and/or Keycloak)

Alternatives

• Only expose Helm Values via this component
• Provide config examples in the documentation

[corvus-ch]

@megian What is your take on this?

I am a bit worried that removing this could potentially brake a lot of set-ups. Before we do this, I would like to have a description on how to achieve the same results currently covered (given they are actually used somewhere).