vSphere support for binary deploys

Aside form working with binary deploys, this PR changes the following two items (vSphere only):

* The reactor on the salt master is configured to run `state.highstate` on *every* node whenever any minion starts. This solves a timing issue introduced with the binary deploys; the master can be done with provisioning much sooner than the minions, meaning the apiserver configuration won't be seeded with the right list of minion IPs. This is solved by running `state.highstate` on minion starts, which causes the apiserver configuration to be rewritten and the daemon to be cycled every time a new minion starts.
* To verify the minions have started from kube-up, the script now polls `http://<ip>:10250/healthz`. The check that is executed from the GCE scripts depends the minions having completed provisioning before the master becomes available. This allows for the case where docker is not yet provisioned, while the master is already responding to requests, which in turn can cause the sanity check to fail.

cc #1732
I agree. I have split the highstate files in: 1) new node only, 2) masters, 3) minions. This allows for a little more fine grained selection of highstates, as some deployments may only want to highstate the new node and the master, instead of everything. In the case of vSphere, we want to highstate ALL nodes because of the static routes. This is then achieved by including all three files in the reactor configuration. I have added this as a separate commit, instead of rebasing it into the vSphere modifications.