A first cut at generating solo.rb from knife.rb

thoughts @tmatilai?
Automatically expanding relative paths in solo.rb
Manifest update
WIP: Using knife.rb to configure and generate solo.rb
Include submodules in manifest
Update manifest
Fix test stub
Use explicit home dir in provisioning path.

Fixes #212
Will probably break windows nodes where shell is cmd.exe-based
Don't nest kitchen directories on the node
Include data bag key in default knife.rb

Just don't try to transfer it if it's missing.
Don't clobber existing knife.rb
Avoid checking data bag secret if option isn't set
Pull out config object

Since we rely on knife.rb and controlling the resulting paths, this config object seemed like more overhead than we need.
Fix path to search cookbook submodule
Manifest fix
Merge branch 'master' into issue/knife-rb-configuration-199

Conflicts:
	Manifest.txt
	knife-solo.gemspec
	lib/chef/knife/solo_cook.rb
Use `config_value` helper for `:provisioning_path`

Allows setting the value in knife.rb with Chef 10, too.
Add optional mode option to `run_portable_mkdir_p`
Restrict permissions of the upload directory

Set the provisioning_path dir mode so that it is not world-readable.
Fixes #1.
Ensure unique names for cookbook directories

Avoid possible collisions between user cookbook directories, our patch
cookbooks and future Berkshelf integration.