This change introduces the concept of Rudders - pluggable modules that
Tiller communicates with via grpc, which allow to decouple orchestration
logic from Tiller into separate service.

This commit consists of simple Rudder implementation which does exactly
the same thing as built in Tiller orchestrator - it creates all k8s
objects from provided manifest without orchestrating them.

--experimental-release flag is introduced to enable this behaviour.

This change allows to use the service and tiller outside of the cluster.
Following commits will add Rudder to helm deployment.

resolves #1927

pulled logic out in pkg/releasetesting

* This is a simple mvp which processes a test definition with the
hook annotation for test when you run `helm test [release]`
* helm client cmd, proto def, tiller logic

This adds a simple description for each lifecycle step on a release
object.

Closes #1661

Closes #1511

This feature allows you to rollback release to the
previous version of release.
resolves #1004

laying ground work for #690

This fixes indentation, documentation, and removes unused protobuf
files.

This commit finally ties `helm install` together with the Kubernetes
client library to make an end-to-end trip.

There were several small fixes to go on both client and server side,
along with some changes to proto to support better error reporting.

The alpine chart has been updated to exhibit how the new Helm works.

This adds support for dry run on install, as well as providing
enough info for an install to display (verbose) manifests. While
doing this, I ended up just storing the rendered manifests for
simplicity.

	1. remove preliminary hapi protocol buffer definitions
	2. modify hapi Makefile
	3. update hapi protobuf model in _proto/hapi/{chart,release,services}
	4. generate protobuf src to pkg/proto/hapi/{chart,release,services}