hooks: Add option to disable TLS verification

[nerg4l]

This PR introduces hooks-http-insecure flag to the CLI and Insecure field to HttpHook struct.

If you are wondering, why ForceAttemptHTTP2: true, was added to http.Transport:

// InsecureSkipVerify controls whether a client verifies the server's
// certificate chain and host name. If InsecureSkipVerify is true, crypto/tls
// accepts any certificate presented by the server and any host name in that
// certificate. In this mode, TLS is susceptible to machine-in-the-middle
// attacks unless custom verification is used. This should be used only for
// testing or in combination with VerifyConnection or VerifyPeerCertificate.
InsecureSkipVerify bool

// ForceAttemptHTTP2 controls whether HTTP/2 is enabled when a non-zero
// Dial, DialTLS, or DialContext func or TLSClientConfig is provided.
// By default, use of any those fields conservatively disables HTTP/2.
// To use a custom dialer or TLS config and still attempt HTTP/2
// upgrades, set this to true.
ForceAttemptHTTP2 bool

Resolves #1335

[Acconut]

Let's do it like this, so we keep the default TLS config for most use cases:

Suggested change

	TLSClientConfig: &tls.Config{
	InsecureSkipVerify: h.Insecure,
	},
	}
	}
	if h.Insecure {
	client.Transport.TLSClientConfig = &tls.Config{
	InsecureSkipVerify: true,
	}
	}

[nerg4l]

Transport is a http.RoundTripper and it would require casting like this. I changed the assignment a bit to avoid it.