fix(tiller): return yaml parsing errors

feat(tiller): add source file to log entries

feat(gometalinter): Move to versioned releases

fix(helm): helm create will not overwrite existing files

feat(charts): Move bucket to domain from path

fix(tiller): show failed YAML

use openssl instead of shasum

fix(helm): respect dryRun opt in DeleteRelease

shasum is not on many platforms (like centos), use openssl instead.

gometalinter has moved to versioned releases. The latest of the v1
major versioned releases can be retrieved through pkg.in. This
change moves gometalinter use to the latest v1 release.

Downloading of charts and helm itself happened over http. This
change moves to use https as that is available with valid certs.

closes: #1519

When an install fails and --dry-run is set, return the broken YAML for
the user to debug.

Closes #1499

fix(helm): replace repo entry instead of duplicating

docs(tiller): add docblocks to public methods

A bucket name in the path can be migrated to a custom k8s domain
name. This is in preperation for that.

It will ignore files if they exist, and create files if they were
missing.

Closes #1515

docs(install_faq): add more info on socat on CoreOS

Closes #1522

docs(chart_template_guide): fix spacing

fix(*): fix new linter errors

fix(scripts): increase deadline for linter

docs(install): fix deployment name in tiller delete command

fix(1516): use correct value reference in boilerplate NOTES.txt

Consistently add spacing for '{{ $foo }}'

docs(chart_tempalte_primer): add template primer

fix(tiller): improve deletion failure handling

ref(ci): cleanup ci deploy

This adds a detailed document on writing templates in Helm. This is NOT
a best-practices guide, but a thorough introduction to templates in
Helm.

This does the following to improve deletion failure handling:

- In an UninstallRelease operation, the release is marked DELETED
  as soon as the basic checks are passed. This resolves 1508. I filed a
  followup issue for doing this even better when we can modify protos
  again.
- If a YAML manifest fails to parse, the error messages now suggests
  that the record is corrupt, and the resources must be manually
  deleted.
- If a resource is missing during deletion, the error messages now make
  it clear that an object was skipped, but that the deletion continued.

Closes #1508