Investigate use of kube-linter and need for new step or not

[itewk]

Purpose

Investigate https://github.com/stackrox/kube-linter and see if it fits in as another step implementer for the validate-environment-configuration step or if it falls into some new category.

Other musings

Currently we run validate-environment-configuration post deployment and use https://github.com/stelligent/config-lint. By guess is that both config-lint and kube-linter can be used post deployment by doing what we do now which is download the namespaces kube state. Buuuuut...... this kube-linter brings to mind that there is probably a reason to add a new step to validate the deployment config BEFORE deployment as well. The reason we are doing it after currently was the specific use case of looking for the runtime injection of a service mesh which can't be found in the static config because is injected by overlay operators at runtime, which means we probalby need both validate-environment-configuration and a new deployment-config-static-code-analysis step or something similar.

[itewk]

@BillBensing @ppremru @dwinchell FYI