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
Aside requiring no action: `highstate` is overkill here but probably okay.  *ideally* we'd run highstate on the new minion and run a targetted 'new-node' state on every other minion.  The [salt docs](http://docs.saltstack.com/en/latest/topics/reactor/) on reactor have examples of this.  But, to be honest, I don't think that we want to go down that path as it'll require more in depth salt knowledge to hack on this stuff.