helm/v3: propogate main application logger to client

[stefansedich]

The Helm V3 code was passing in klog.Infof for the logger which meant that we were missing out on formatting the internal helm logs using our configured logger and the users logging preferences.

This change creates a logging function to mimic klog.Infof and simply routes it to our logger as an info level log.

Example of logs being consistent across both our components and the internal helm logs.

ts=2020-01-21T18:43:25.501926825Z caller=operator.go:307 component=operator info="enqueuing release" resource=opa:helmrelease/jupyterhub
ts=2020-01-21T18:43:25.603914422Z caller=release.go:353 component=release release=podinfo-child targetNamespace=opa resource=opa:helmrelease/jupyterhub helmVersion=v3 info="performing dry-run upgrade to see if release has diverged"
ts=2020-01-21T18:43:25.606268155Z caller=helm.go:167 component=helm version=v3 info="preparing upgrade for podinfo-child"
ts=2020-01-21T18:43:26.00569832Z caller=helm.go:167 component=helm version=v3 info="performing update for podinfo-child"
ts=2020-01-21T18:43:26.010283371Z caller=helm.go:167 component=helm version=v3 info="dry run for podinfo-child"

Closes #226

[hiddeco]

Thanks Stefan 💯