Windows Support, and HTTPS fix

[thebeline]

1. Adds support for Long Path names and Symlinks for Windows VirtualBox.
2. Ensures that Chef Solo only runs on VirtualBox (only supported).
3. Resolves an HTTPS error when forking Chef:

==> default: Running chef-solo...
==> default: stdin: is not a tty
==> default: [2015-04-27T18:47:43+00:00] INFO: Forking chef instance to converge...
==> default: [2015-04-27T18:47:43+00:00] WARN:
==> default: * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
==> default: SSL validation of HTTPS requests is disabled. HTTPS connections are still
==> default: encrypted, but chef is not able to detect forged replies or man in the middle
==> default: attacks.
==> default:
==> default: To fix this issue add an entry like this to your configuration file:
==> default:
==> default: ```
==> default:   # Verify all HTTPS connections (recommended)
==> default:   ssl_verify_mode :verify_peer
==> default:
==> default:   # OR, Verify only connections to chef-server
==> default:   verify_api_cert true
==> default: ```
==> default:
==> default: To check your SSL configuration, or troubleshoot errors, you can use the
==> default: `knife ssl check` command like so:
==> default:
==> default: ```
==> default:   knife ssl check -c /tmp/vagrant-chef/solo.rb
==> default: ```
==> default:
==> default: * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
==> default: [2015-04-27T18:47:43+00:00] INFO: *** Chef 11.16.0 ***
==> default: [2015-04-27T18:47:43+00:00] INFO: Chef-client pid: 1467
==> default: [2015-04-27T18:47:50+00:00] INFO: Setting the run_list to ["recipe[startupgenome]"] from CLI options

Sorry that there are a number of commits for what amounts to a small change, as a first foray into Vagrant, it was quite the learning experience.

[TomWoodward]

:cake:

[thebeline]

@sudo-reboot - yeah, not so fast, I bunked up the symlink.

[thebeline]

Oh wait, no i didn't... ok, good. phew.