search prerelease gems for subcommands

- otherwise we can't test knife gem rc releases
Merge branch 'contributions'
Skip IPv6 tests on Solaris

Some supported Solaris platforms are too old for IPv6. Most of the risk
in the code paths being tested exists in the userland code, so we expect
to have adequate coverage as long as the tests run on some platform.
Always set a correct Host header to avoid net/http bug

Net::HTTP fails to surround IPv6 addresses in brackets when constructing
a Host header. Net::HTTP respects any user-supplied Host header, so we
ensure that the Host header is correctly formatted by setting it
manually for all requests.
Merge pull request #1099 from opscode/lcg/knife-subcommand-prerelease

search for prerelease knife gems as well
[CHEF-4842] Fix comparison of user resources with non-ASCII comments

In case a comment of a user resource includes non-ASCII characters, the
comparison whether the resource was changed will always fail. Therefore,
such user resources will get modified during every chef-client run.

Example:

    user "marci" do
      comment "Márton Salomváry"
      # ...
    end

So far, this resulted in a comparision of "M\xC3\xA1rton
Salomv\xC3\xA1ry" with "Márton Salomváry" which fails, unless the
encoding gets changed prior to the comparision.
Merge pull request #1156 from soundcloud/fix-user-resource-comparison

[CHEF-4842] Fix comparison of user resources with non-ASCII comments
Split EncryptedDataBagItem into multiple files
CHEF-4441: emit reasonable error message when there is no default data bag secret
Merge branch 'jk/CHEF-4441'
print total number of resources as well
Merge pull request #1162 from ranjib/CHEF-4852

[CHEF-4852]Print total number of resources in doc formatter
Add ability to run recipes directly from chef-client command line
Bump version to 11.10.0.alpha.1
bump up upper limit on json gem to 1.8.1
Merge pull request #1179 from opscode/lcg/CHEF-4632

bump up upper limit on json gem to 1.8.1
remove debugging puts
CHEF-4849: Implement `#response_file_variables` in Package resource

Now that Chef properly supports a package `response_file` using
`Chef::Resource::Template`, the Package resource should implement the
`response_file_variables` method so that variables do not have to exist
as node attributes (eg - for seeding DB passwords for configuration
files generated by packages).