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!
This issue now appears to be a red-herring IMO. With the response now coming back as "null" upon resource not being found jclouds successfully returns this as a null object instead of throwing an error trying to convert it to json. I think we are safe moving forward with no needed Fallback implementation or returning of null on 500. I think this is as happy a path as we can expect.