update net-ssh and net-scp dependencies to use recent dependencies

[erikh]

you may be aware that net-ssh's author has pushed changes which break many pessimistic gem requirements.

http://solutious.com/blog/2013/02/06/net-ssh-gem-code-signed/

several tools like fog, chef, etc depend on these gems, and updated gems have been pushed to reflect the dependency.

Here's a post which explains the upgrade from opscode's point of view:

http://jtimberman.housepub.org/blog/2013/02/06/chef-and-net-ssh-dependency-broken/

Unfortunately I can't use vagrant with my other tooling in bundles, etc because of this.

I ran both the units and acceptance tests before and after the spec change -- there was no difference in the test output, although several acceptance tests failed before and after it.

I'm inclined to think there's no reason to avoid changing this, and the sooner the better. :)

[mitchellh]

I cannot merge this back into 1-0-stable. I refuse, unless there is a significant security risk and thorough testing, to make a 2.2 => 2.6 version upgrade in a dependency of a stable release of Vagrant.

I'm willing to look at this change for master.

But note that the net-ssh gems fixed the dependency issues with regards to what Vagrant is dependent on, so things are fine there. Interop with other programs should be done via shelling to an installer-based Vagrant which has its own private Ruby, which avoids gem collisions there as well.

The main issue is if you're using the gem install vagrant, you're gonna have a bad time. This is why Vagrant 1.1 forward won't have a gem install anymore.