TLS support for boot2docker 1.3.0 and support for include pattern for tar used as docker context

[ahmedomarjee]

• boot2docker 1.3.0 seems to require TLS, fixed url and added certificates and keys for dockerode to make a connection
• the start cluster command needs to set a content-type of application/json for it to work
• it is useful to use include patterns to reduce the size of the tar used as docker context (opted to use an include pattern rather than an exclude pattern since it should be a smaller subset of files)
• incremented version of plugin

[ahmedomarjee]

Needed to mention that this changes the decker.json format slightly to support the includes pattern.

With a little more effort we could probably support both styles.

So instead of:

{
    "images": {
        "decking/example-api": "./docker/api",
        "decking/example-admin": "./docker/admin",
        "decking/example-web": "./docker/web"
    },
.
.
.
}

we need to use:

{
    "images": {
        "decking/example-api": {
            dockerfile: "./docker/api",
            includes: ["dist"]
        }
        "decking/example-admin": {
            dockerfile: "./docker/admin"
        },
        "decking/example-web": {
            dockerfile: "./docker/web"
        },
    },
.
.
.
}

[ahmedomarjee]

There is a bug in the includes pattern, also added support for both old and new decking.json format.

Fixed in a later pull request.