TLS dialer

[munakoiso]

Hello.

Here is an implementation of a dialer using tls connect.
Also I have added a function which returns a simple tls.Config. This is probably the most common way to create it, so I decided to put it in this library.

I think it might be useful.

Usage example:

	tlsConfig, err := zk.CreateTLSConfig(rootCAFile, crtFile, keyFile)
	if err != nil {
		fmt.Println(err)
		return
	}
	timeout := 1 * time.Second
	baseDialer := net.Dialer{Timeout: timeout}
	dialer, err := zk.GetTLSDialer([]string{"hostname:2281"}, &baseDialer, tlsConfig)
	if err != nil {
		fmt.Println(err)
		return
	}
	conn, _, err := zk.Connect([]string{"hostname:2281"}, timeout, zk.WithDialer(dialer))

[munakoiso]

Hi, @nemith . Can you review this PR please?

[nemith]

I am not longer a maintainer on this project

[munakoiso]

@nemith
Oh, sorry, but I can't find any information about maintainers here.
Maybe you can tell me who are maintainers?

[jeffbean]

nit: since this is used in the function below, this function would be sorted below it.

[jeffbean]

This should not assume files, and have io.Reader as input for all three inputs. This allows a better library experience having tests and callers pass in content as they see fit.

also the tls package allows this to work then with https://pkg.go.dev/crypto/tls#X509KeyPair

[jeffbean]

is this function then used as the option to use as an option? The notion would normally be that the surrounding library would pass in this dialer themselves. If we wanted to support TLS Dial in the zk lib. I would want to have this outside the main zk package and in a supporting package