Don't force SSL for username+password #155
Description
The configuration screen currently will not let you proceed if you configure password authentication but don't enable SSL.
Consider adjusting this to just show a really big warning instead of outright blocking it
My use case is hosting Metabase and Trino within the same Kubernetes cluster, where secure networking between services within the cluster is provided. In order to enable SSL, I have to point the connection string at a public Ingress URL where TLS gets terminated and have all the traffic go through our public load balancer for no reason. The best security practice is to connect directly between services through cluster service hostnames with security handled at the TCP layer already.