JCLOUDS-782: init for shipyard provider

Initial commit for shipyard provider. My intent was to have the entire provider coded and in something like "good working shape" before I submitted a PR but @nacx strongly suggested I not do this.

This code base is a fork of the work @andreaturli is doing with docker so there may be more than a few similarities. Shipyard itself is essentially a docker manager allowing users to connect N number of engines (docker daemons) to a single source allowing you to work with them from a single location. A few points to note:

-There are literally no testers at this point. Working on this...
-Around 10 files or so are json that gets handed back from shipyard. Used for testing purposes and do not need to be looked over.
-The idea here is to implement the entirety of ComputeServiceAdapter. All methods except 'createNodeWithGroupIntoName' have been coded. Working on this...
-All 'listNodes*' methods are being ignored. Not entirely sure why...

shipyard API can be found here: http://shipyard-project.com/docs/api/

So with that said please take a peek and let me know what you think!
So this is my ... sad ... attempt at making sure one does not pass in OpenStack like credentials (e.g. <some.project>:<some.username>). It was mainly to code against something I had found here, where we use OpenStack and Shipyard, in that we provide a higher level API on top of jclouds and found that some users, who were familiar with OpenStack, passed in the same identity format for shipyard. It should have been addressed in the higher level API but I did so here in my efforts to understand how jclouds works. I'll remove.