Defer validation of Kubernetes environment until a resource effectively needs it

We'd like to integrate the bootstrapping of our Minikube cluster to Tilt using local_resource

This is helpful because we can dynamically determine how cpu/memory to use based on which resources need to be deployed, and also because currently, our way to setup a local development environment is finnicky (i.e. wait until this service is up, then port-forward it to :XXXX, then run this JAR to register the IoT device on the cluster...) and we'd like to make that into a single tilt up command, especially given that "waiting for service X to be up" is the kind of thing that is finnicky to script, but that Tilt is great at.

Currently, however, when you tilt up before Kubernetes is up, you'll run into some variation of these errors:

Error: Error watching k8s events
: could not set up k8s client: Kubernetes context not set in [/home/ubuntu/.kube/config]

Error: Error watching services. Are you connected to kubernetes?
Try running `kubectl get services`: could not set up k8s client: Kubernetes context not set in
[/home/ubuntu/.kube/config]

This will happen even though we have a local_resource that will spin up a minikube instance, and if this check was deferred by default (or by some top-level setting like deferred_kubeconfig(True)) this could be naturally implemented and would work as intended

Start by reproducing the reported tilt up behavior before Kubernetes is available, using a local_resource that starts Minikube. Trace where Kubernetes validation occurs relative to resources that need it, then define and test the requested deferred behavior or top-level setting so startup does not fail until a resource effectively requires Kubernetes.