Fix issue with kube context not being set for vpn commands

[bmonkman]

Recent VPN commands are using kubectl after setting up the cluster and the kube context, but we don't actually switch to the next context after we create it so any kubectl commands will fail.
We should probably add the --context argument to any kubectl commands we are running manually as part of zero apply.