[WIP] Add support for Config{} to kubecfg

This PR will allow users to use simple JSON file with arrays of Kubernetes objects (services, pods, replicationControllers) as a parameter for `kubecfg -c config.json apply` command.

The [example JSON](https://github.com/mfojtik/kubernetes/blob/config/examples/config/guestbook.json) file in `examples/config/guestbook.json` contains all objects required for deploying the [guestbook example](https://github.com/GoogleCloudPlatform/kubernetes/tree/master/examples/guestbook).
We really need to think about ordering for something like this. Some pods may depend on some services. Can the pod handle it if it starts before its dependencies? Clearly the right answer is "yes it should", but only the human setting up the system knows this.

I suppose it's probably fine to say that this only works for pods where start order doesn't matter. The human can always sort their services/pods into batches and start each batch with this method. But we should explicitly say this somewhere.