Make "kubecfg -s <port> run ..." select correctly

kubecfg run creates a replication controller which sets all pods with a
replicationController= label, but then sets up a service selecting on name=
instead.  This fixes that.  kubecfg -s <port> run ... can now actually work.
The thing to keep in mind is that `run` takes a parameter named `controller` for this name.  It looks odd when we then have a pod with `simpleService=fooController`.  This is why I named the label `replicationController`.

And I totally regressed the `servicePort` flag.  Sorry about that.  I didn't read the code closely enough to realize we had this option. It wasn't used in the samples/e2e tests.