Break up version feature

MSP-11103

Group similar scenarios into their own features.
Fix typo

MSP-11103
bundle install after adding development dependencies

MSP-11103

`bundle install` after adding the development dependencies to ensure
that metasploit-version and rspec are available in the bundle so the
user can immediately use metasploit-version.
metasploit-version install sets up rake spec

MSP-11103

metasploit-install will setups `.rspec`, `spec/spec_helper.rb`, and
`Rakefile` so that `rake spec` will work after `metasploit-version
install` runs.
Use clean gemset for all metasploit-version install features

MSP-11103

Need to use a clean gemset since `metasploit-version` install does a
bundle install after adding metasploit-version as a dependency to the
scenario's gemspec.
Update to release childprocess through updated aruba

MSP-11103
Default --patch to 1

MSP-11103

PATCH must default to 1 because pre-releases of 0.0.0 are invalid as
they are < 0 and the default version requirement is >= 0.  Having PATCH
1, makes the default version 0.0.1, which makes the pre-releases be > 0
and < 0.0.1.
install version_spec.rb

MSP-11103

Generate template for version_spec.rb, which will check that version.rb
is compliant when updated by metasploit-version or manually.  Features
check that version_spec throws correct errors when version.rb isn't
updated correctly and that by default users can run `rake spec` after
running `metasploit-version install --force` and it will work.