Check exit codes of puppet provisioners

Previously, failures in applying the puppet manifests would be
ignored, because puppet apply/agent don't have any useful exit codes
by default.  (Errors are printed, but vagrant continues.)

Use the option --detailed-exitcodes of puppet apply/agent to check for
success.
Fix Windows shell provisioning

Resolves [GH-1036] [GH-1164] [GH-1181]
Merge pull request #1182 from obscurerichard/fix-windows-shell-provisioning-vs-1-0-stable

Fix Windows shell provisioning
Update CHANGELOG and whitespace
Update version
Merge pull request #1180 from maestrodev/v1.0.5-exitcodes

Check exit codes of puppet provisioners
Update CHANGELOG
Fix DNS resolution bug for 12.10 [GH-1176]
Allow hostname to be a substring of the guest name on Ubuntu [GH-1163]
Become Puppet 3.x compatible [GH-1169]
Work around bug in OS X 10.8 and VirtualBox wrt VBoxManage

OS X 10.8 introduced a bug where on setuid/setgid executables, it will
print a warning to stdout if any DYLD_ enviornmental variables are set
(most common being DYLD_LIBRARY_PATH).

VirtualBox, specifically VBoxManage, sometimes shells out to external
programs to do some work, reading stdout for the result. The warnings
injected by OS X cause VirtualBox to read bad values, breaking Vagrant.

These work around both of these issues. Great.
Update gemspec to not require git for new vagrant installers
Clean LD_LIBRARY_PATH prior to calling VBoxManage as well
Remove dependency of VirtualBox for running tests
v1.0.6
Update CHANGELOG