Support an alternative naming scheme for load balancers

Currently we make use of the service's UID. The problem with that is we can't use products like heptio ark to do cluster restores since clients cannot set the UID of a resource (restricted by the api server). The problem is you can associate the load balancer back to the service in the new cluster w/o manual intervention to rename the load balancers. Alternatively, if we allow the load balancer to be named something like (<optional prefix>-)<namespace>-<service> we can associate an existing load balancer with a given service after restore.

Proposal:

Add an optional configuration argument to use an alternate naming schema. The default will remain UID. If the flag is enabled then we'll first attempt to fetch the load balancer by name then if that fails attempt to fetch the load balancer by uid for backwards compatibility. That gives an upgrade path (albeit manual) to migrate existing LB's to the new naming schema if they want.

cc @prydie

No files or tests are named. Start by locating the load-balancer naming and lookup entry points, then find how optional controller configuration is defined; done means supporting the proposed name-first lookup with UID fallback while preserving the default UID behavior and upgrade path.