[Story] Support Services without Ingresses or Routes

Our Helm chart currently allows users to install Cryostat using only Services for networking, with some additional post-install steps required. It would be useful if the operator could also support these use cases, without the post-install steps.

We would want to support `ClusterIP`, `NodePort` and `LoadBalancer` services. At least for `ClusterIP`, we would need to add some kind of "external URL" property to the Cryostat CRD. This would allow the user to inform the operator of what `host:port` the services are port-forwarded to. This is needed so Cryostat can set up the notifications WebSocket connection and also to launch Grafana.