Remove redundant kubeconfig copy on AWS and GCP

* AWS and Google Cloud make use of auto-scaling groups
and managed instance groups, respectively. As such, the
kubeconfig is already held in cloud user-data
* Controller instances are provisioned with a kubeconfig
from user-data. Its redundant to use a Terraform remote
file copy step for the kubeconfig.

digital-ocean/container-linux/kubernetes/ssh.tf

@@ -81,7 +81,7 @@ resource "null_resource" "copy-worker-secrets" {
     content     = "${module.bootkube.kubeconfig}"
     destination = "$HOME/kubeconfig"
   }
- 
+
   provisioner "remote-exec" {
     inline = [
       "sudo mv $HOME/kubeconfig /etc/kubernetes/kubeconfig",