Eureka server is itself a eureka client when discovering eureka peers (it gets DiscoverClient from DiscoveryManager).  Make sure DiscoveryManager is initialzed regardless of if the client or server config is invoked first.

fixes gh-18

Add support for Ribbon loadbalancing in RestTemplate via an HttpRequestInterceptor that when supplied a uri such as http://myservice/my/endpoint (where myservice is a service as defined in a service registry, such as Eureka), it replaces 'myservice' with the actual host and port as returned from the configured ribbon loadbalancer.

closes gh-12

Without extracting to autoconfig the @ConditionalOnMissingBean won't
always work because it is dependent on the order of the configuration
classes being processed (and autoconfig always somes last).

Because we were using Lifecycle to kick off the eureka registration the
local server port wasn't available yet. The change is to use an
ApplicationListener and listen for the event that contains the container
with its port instead.

Fixes gh-15

The problem is pretty deep here so I hope I did something sane. Basically if
PeerAwareInstanceRegistry.openForTraffic(int) ever gets called with a 0 argument
it resets the threshold for numberOfRenewsPerMinThreshold to 0 from which
it only ever recovers if the same method is called again with a non-zero argument.
For a standalone server this means that it will never automatically expire
any leases (only when it chats to its neighbours and finds out they have
registered services will it ever switch the threshold back on).

Another problem (unsolved) is that the reset mechanism will kick back in
occasionally (resetting to 1 with this change, but that's probably also
a bad thing). And when there *are* actually peers to talk to unless they are
in AWS they will never communicate correctly about the actual number of local
services (the criteria for that are deeply connected with AWS and EIP).

Fixes gh-6