Documentation: clarify the difference between --no-tlsverify and --no-tls

[stuclem]

Following a question from @mreferre:

We do currently state that --no-tlsverify only creates/uploads server certs, and that clients are unverified. However, the writeup of --no-tls states pretty much the same about the client side and doesn't say much about the absence of a server cert. We need to make it 100% clear that with --no-tls there is no server cert. In other words, with --no-tlsverify, any client can connect, but at least the connection between the client and server is a secure one. With --no-tls, any client can connect, and the connection itself is insecure.

@hickeng is this accurate?

[stuclem]

Covered by vmware/vic-product#70. Closing as a dup.