windows workflow improvements
on windows automatically elevate to admin privileges if needed and attempt to use git's bundled ssh if ssh not found
this makes the vagrant up and vagrant ssh commands work without requiring extra effort from the user on a windows host
Windows doesn't ship with a compatible ssh executable. Git installer on windows doesn't add git bin dir to the system path by default because it causes conflicts with windows built ins. The batch script makes git's bundled ssh usable in the vagrant context in this case. It defaults to ssh on the path if there is one
The vagrant.bat wrapper handles automatic privilege escalation which is necessary on windows to have the permissions to create symlinks in the shared folder.
This currently uses the command prompt for windows it opens. A future commit could use the command prompt or power shell depending on which the user is calling from.