Delete Chef client and node on cleanup

This fixes #1253 by shelling out to `knife` on cleanup, as per
@mitchellh's suggestion in #1255
Show node name in logging
Suppress knife output
Allow non privileged user vagrant to run a shell provision
pushing salt provisioner
respect :nic_type option for private network. Fixes #1704
Merge https://github.com/mitchellh/vagrant into salty-vagrant-provisoner
added most recent version of salty-vagrant and bootstrap.sh
Defining the group of a shared folder

Symtom: The group ID for groups that are not backed by a user account (e.g. admin) cannot be obtained from the id command.

Consequence: The shared folder group can only be set to a group where by a user account of the same name exists.

Solution: Correcting the method to define the group ID by looking up the group ID via the group name.
Updating provisioner to use latest bootstrap script
Merge branch 'master' into salty-vagrant-provisioner
Generate ansible_hosts file if one is not provided
support for chef solo environments, upcoming in chef 11.6
adds extra verbosity option to ansible provisioner
Added solaris11 guest plugin
Updates Chef provisioner configuration option formatter for Chef 11

Refs #1250.

Will correctly produce the desired result on Chef 11.x and above, as the
original directive was written against Chef 10.x, and released in Vagrant 1.2.7.

While this will continue to work for Chef 10.x, since this is not the 'mainline'
release track, and the alternative would be to write more conditional code in
the configuration file to detect the version and place the correct directive, this
changes the directive to support the current releases of Chef 11 and above.
allow port-forwarding of the same port number but with different protocols [GH-1108]
fix broken regexp from 2a9d0c9
Merge pull request #2084 from glensc/fix-2a9d0c9

plugin/hosst/fedora: fix broken regexp from 2a9d0c9
more capabilities for OpenBSD guest