systemd example unit and environment files

The binary names in these are

kube-apiserver
kube-controller-manager
kube-scheduler
kube-proxy
kubelet

The environment/config files need to live in /etc/kubernetes/

I personally like the namespaced binaries a lot more than just 'apiserver' etc.  I wouldn't mind if we switched the binary names to something namespaced in the in project build...
When we populate the service env variable for a container (in [GetServiceEnvironmentVariables](https://github.com/GoogleCloudPlatform/kubernetes/blob/343677580a5af96e700c8b191245a23a8b178387/pkg/registry/service/rest.go#L195)) we *were* using the IP address/name of the minion as far as the api server knew it.  If the "name" of the minion that the apiserver sees is `127.0.0.1` then we would use that value to try and point the code int he container at the proxy.  But it couldn't get to the proxy as the `127.0.0.1` *inside* the container would mask the `127.0.0.1` of the host.  I suspect now that we have IP-per-Service this issue no longer applies.