Initial implementation of Config creation

This PR contains initial support for Config creation for the Origin `kubecfg` client. There is an example Config JSON (same format as you get when you use templateConfig for generation).

To try this out, you can execute this command:

```
$ openshift kube apply -c pkg/config/example/config.json
```

The the client will create the resources in following order: Services, Pods, ReplicationControllers. 

FYI: This PR bundles https://github.com/openshift/origin/pull/41 because I need Config{} object.
The question is, what we want from our `Config{}` functionality until upstream merges their `Config{}`.
Imho, `Apply()` should check the `Config.ID` and `Config.Name` fields and validate the all `Items` (depending on their "kind"), so the `openshift kube -c file.json apply` command errors out right away. Also, it should check for already existing resources in k8s, so it fails immediately rather than creating k8s tasks that are going to fail anyway. It's just for user convenience. I can imagine someone doing the DEMO on Nov, trying to create new project from Template/Config using the `kube apply` and having troubles because of missing error messages, explaining what was wrong. Or would you prefer him/her looking at the k8s logs instead / querying resources?