Better KUTTL Testing Context

[kensipe]

Recent challenges by new KUTTLers, it was hard to know:

1. Was the connection with kubernetes cluster working and
2. Was kuttl pointing to the correct location for tests

This PR resolves that... KUTTL previously had connect failure messages with:
Bad local config

 harness.go:572: fatal error getting client: invalid configuration: no configuration has been provided, try setting KUBERNETES_MASTER environment variable

or bad connection with:

harness.go:572: fatal error getting client: Get "https://127.0.0.1:63473/api?timeout=32s": dial tcp 127.0.0.1:63473: connect: connection refused

However... the absence of this doesn't reinforce comfort... this PR adds the following message after a good connection:

 harness.go:274: Successful connection to cluster: https://127.0.0.1:63473

Additionally, it is hard to know if users are pointing their testsuite dir to the right location... Adding in a message that will indicates that:

harness.go:354: testsuite: /Users/kensipe/projects/playground/e2e has 1 tests

Signed-off-by: Ken Sipe kensipe@gmail.com

[ANeumann82]

Looks good. I'm always up for more logging ;)

[porridge]

WDYT about refusing to run a suite with 0 tests @kensipe ?