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

### The pull requests consists of the following :

* support for boot2docker 1.3.0
  * requires TLS
  * fixed url and added certificates and keys prior to making docker connection using dockerode
  * the start cluster command needs to set a content-type of *application/json*

* reduce size of tar built as docker context
  * added an optional includes pattern to specify paths that should be included in the tar
  * the property is optional, if not specified, reverts to default behaviour, whee entire working folder is added to tar
  * opted to use an include rather than an exclude, given it would be mostly likely be the smaller dataset

* incremented version of plugin

## Example

So instead of:

````
{
    "images": {
        "decking/example-api": "./docker/api",
        "decking/example-admin": "./docker/admin",
        "decking/example-web": "./docker/web"
    },
.
.
.
}
```

we can also use:
```
{
    "images": {
        "decking/example-api": {
            dockerfile: "./docker/api",
            includes: ["dist/"]
        }
        "decking/example-admin": "./docker/admin",
        "decking/example-web": "./docker/web"
    },
.
.
.
}
```

## Notes

1. The docker file referenced in *decking.json* will always be included in the tar archive.
2. The old and new syntax can be used side-by-side providing backwards and forwards compatibility.