bug: if local machine has a kind installation already, porter fails

If you have a kind cluster up locally, `porter install --param cluster-type=kind` fails to proceed. I did not have a chance to debug thoroughly, but the fix locally was to delete my existing kind cluster, which allowed the installation to proceed. We need to figure out where/why the clash was happening.