Consider recommending vagrant-wrapper RubyGem in README

[babelop]

At present there's a recommendation in the README that the older vagrant gem may need removed if there's a versioning problem due to PATH issues. Consider as an alternative recommending using the "vagrant-wrapper" RubyGem, either manually gem install vagrant-wrapper or via a Gemfile.

It prioritizes packaged versions of Vagrant in new projects, without breaking legacy projects which still require the vagrant gem. No code changes are required, so long as the wrapper is installed and the given project does not list the old vagrant gem via its Gemfile (or doesn't have a Gemfile).

The 1.0.7 gem gets reinstalled so easily by bundled projects, and many people are still preferring Gemfile's, even though there's a push to eliminate them in Kitchen projects now. So it can be a nice workaround to needing to keep uninstalling the old gem.

[fnichol]

Sounds like a good idea, and thanks for the recommendation!