Berkshelf 3 Fixes - Logging and Output

:construction: 

Now that we have a working berkshelf-api, lets see what shakes out of the master branch of Berkshelf.

* Celluloid outputs some interesting logging with Ridley - I was able to replicate the same "annoying" logging on the simplest of code, so at the moment I am operating under the assumption that Celluloid is just too noisy. On my machine, at runtime, when Ridley code is being executed by Berkshelf, `Celluloid.logger` is an instance of `Kitchen::Logger`. (I seem to remember a debate on test-kitchen as a dependency :wink: )

Adding an example of the Celluloid output I've been seeing (I added a puts to output the value of Celluloid.logger):

```
Installing java (0.1.16) from https://our-chef-server:443/organizations/riot (via localhost)
Celluloid Logger is #<Kitchen::Logger:0x007f919bdb0f18>
$$$$$$ Terminating task: type=:finalizer, meta={:method_name=>:__shutdown__}, status=:callwait
$$$$$$ Terminating task: type=:finalizer, meta={:method_name=>:__shutdown__}, status=:callwait
```

* Human logging and JSON logging should show more info about the source. Here is an example:

```
Installing java (1.12.0) from http://cookbooks.opscode.com/api/v1 (via localhost)
Installing nginx (1.6.0) from http://cookbooks.opscode.com/api/v1 (via localhost)
Installing artifact (1.6.1) from http://cookbooks.opscode.com/api/v1 (via localhost)
```