Prepare Kantra to integrate with the new provider

[mansam]

This provider has different needs from the Java provider, in that rather than a source directory or a binary it requires coordinates to a cluster and a set of namespaces and GroupVersionKinds to analyze. I assume we'll need to add a new CLI command and some machinery to pass along these parameters, plus whatever might need to be done to talk to a provider that isn't the Java one. We could probably get away with adding a k8s specific command, but we should probably keep general platform awareness in mind.

[eemcmullan]

We could add a new kantra subcommand such as kantra k8s-analyze (not set on that name) so that we can easily pass these parameters without running analyzer-lsp. We will need the Dockerfile first to run this as a container.

Also, kantra and analyzer-lsp use cobra https://github.com/spf13/cobra to implement the cli. It may be worth considering using that as well with the k8s-provider.

[mansam]

That plan makes sense to me, as does the suggestion to use cobra for the CLI.