add possibility to setup a custom logger for kubectl configuration

[lahabana]

Description

Fixes #1383.

This enables users to not log messages like: "Configuring Kubernetes client using config file"

TODOs

Read the Gruntwork contribution guidelines.

• Update the docs.
• Run the relevant tests successfully, including pre-commit checks.
• Ensure any 3rd party code adheres with our license policy or delete this line if its not applicable.
• Include release notes. If this PR is backward incompatible, include a migration guide.

Release Notes (draft)

Added option ConfigLogger in KubectlOptions to specify a custom logger for configuration

Migration Guide

[lahabana]

@denis256 any chance to get that in?

[denis256]

Hm, what will happen if the logger will not be provided?

[lahabana]

The logger falls back to the Default logger if it's nil. This also enables backward compatibility

terratest/modules/logger/logger.go

Lines 63 to 70 in 6fb8605

	// methods can be called on (typed) nil pointers. In this case, use the Default function to log. This enables the
	// caller to do `var l *Logger` and then use the logger already.
	if l == nil || l.l == nil {
	Default.Logf(t, format, args...)
	return
	}
	l.l.Logf(t, format, args...)

[lahabana]

@denis256 sorry I didn't notice you commented on the PR.

[lahabana]

@denis256 friendly ping on this :) It would greatly help our test logs to be a lot more readable :)