Kibana ssl configurations should be consistent with the rest of the stack

[epixa]

Each product in the stack handles TLS/SSL settings differently, but we should move toward consistency. Toward that end, we should update Kibana's SSL settings to be the following.

Description	Setting	Default	Valid values
enabled setting	ssl.enabled	false	true, false
verification mode	ssl.verification_mode	full	none, certificate, full
supported protocols	ssl.supported_protocols	TLSv1.2, TLSv1.1, TLSv1	TLSv1, TLSv1.1, TLSv1.2
client authentication	ssl.client_authentication	none	none, optional, required
cipher suites	ssl.cipher_suites	see list below	language specific
certificate authorities	ssl.certificate_authorities	language/system trusted CAs	array of paths to PEM encoded certificates
key	ssl.key		path to PEM encoded key file
key password/passphrase	ssl.key_passphrase
certificate	ssl.certificate		path to file containing server certificate and optionally includes cert chain

All existing non-confirming configurations for SSL should be deprecated with a warning but should otherwise remain functional.

In Kibana, we need to do two different sets of configuration: one for the connection to the browser and one for the connection to elasticsearch. In each case, we should just prefix the relevant configurations as we already have been doing.

[kobelb]

Closing as #9823 was Merged.