Proposal: Separate desired and current states

Speculative change for some items from #1200:

* Metadata that applies to resources is split from APIMetadata on non-resource API objects
* Metadata is a sub field of objects
* Labels are on Metadata
* Pod current and desired state is split
* Name is used for pods instead of ID (UID is part of metadata, Name is part of resource) for idempotent creation #148 and #1216 
* PodTemplate is a Metadata carrying object as per #170
 * If replicationController gave way to a generic "replicator", then pod template could be both a nested struct and a real resource.
* A ScheduledPod and ScheduledPodList is what the kubelet sees as per #860
* Non-schema'd k/v values on Metadata as `Config` (better names welcome) as per #1201

Not changed yet:

* ReplicationControllers
* Services

Only look at the second commit, the first is just to get a nice diff from v1beta1.
Restart count would be useful to users, also, via the apiserver.

In the long run, I don't want to rely on docker inspect output for anything important. We should have our own representation. Docker inspect output could be treated as a plug-in extension. That is an API that has it's own versioning, etc., and I also want to leave the door open for non-Docker containers some day, in case we or a partner has some legacy format they'd like to wedge into Kubernetes.