Eureka ServerConfiguration is now auto-configuration based, instead of being explicitly specified via configuration pulled in through @EnableEurekaServer. This way specific beans can be conditionally overridden, configuration can be re-ordered.
Supports PeerEurekaNodes bean to be overridden by the user

Fixes gh-1717

fixes gh-1616

Fixes gh-1546

fixes gh-1285

Fixes gh-1205

so they don't appear on the dashboard

Fixes gh-974

Fixes gh-642

fixes gh-589

get's eureka branding back.

fixes gh-627

fixes gh-527

Remove Servo from EurekaHealthIndicator.
Remove custom DataCenterInfo.
EurekaInstanceConfig.SID is now used as eureka id.
EurekaInstanceConfigBean.getSID falls back to metadataMap.instanceId for
backwards compatibility.

Fixes gh-117

fixes gh-100

Blitz4j is definitely preventing the log levels from being changed at runtime
through the normal Spring boot channels.

Fixes gh-48

Blitz4j is definitely preventing the log levels from being changed at runtime
through the normal Spring boot channels.

Fixes gh-48

Most browsers support <base href="..."> these days and there
was one already in statut.ftl (but not in navbar). Added a test
that asserts the css is loadable as well.

Fixes gh-55

All static content is excluded in the Jersey config, so we can use
/eureka for the prefix to the Eureka API (i.e. /apps etc.)

Fixes gh-44

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