When click one of the up and running instances this should open the actual instance in separate tab

If the configserver registers with securePortEnabled=true we should
respect that in the discovery process.

Fixes gh-450

Change EurekaInstanceConfig.getSID to getInstanceId

fixes gh-554

Set the default sid from common properties.

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.

And also when using eureka-first for discovering config server.
The EurekaClient is very rigid and initializes itself, registering
with the remote service on instantiation. Hance it needs to be
in @RefreshScope for it to be properly refreshable. Doing that
leads to a sequence of other changes (e.g. to account for the
fact that there is no @RefreshScope in bootstrap context).

Fixes gh-551

fixes gh-534

When the parent (bootstrap) context registers the app as well as consuming
the registry it causes problems, e.g. when you refresh that context is
re-created and destroyed, which tends to unregister the app and it's hard
to get it back. It is simpler if the parent context use eureka read-only.
To ensure this we have to remove the @EnableDiscoveryClient from the
bootstrap context.

Tested with vanilla config server and eureka with the 'eureka-first'
sample and the 'zuul-proxy-eureka' sample.

Fixes gh-421

Reverts part of a change made for gh-349 and rationalizes a bit of the
Eureka configuration. The Eureka client cannot be shutdown without
attempting to restart it (but there isn't an obvious public API for
that), so it's better not to shut it down at all.

See gh-421

Move turbine/hystrix amqp specific implementations to spring-cloud-stream based implementations and let the user decide which broker to use.

fixes gh-545

1.4.15 isn't in maven central yet

fixes gh-534

fixes gh-540

see gh-539

fixes gh-535

* CPGFinanceSystems-master:
  Add X-Forwarded-Proto HTTP header to zuul proxy requests

If the zuul reverse proxy and the destination services are using a different scheme
(for example HTTPS on proxy side and HTTP on service side) an additional HTTP
header is required according to RFC7239 [http://tools.ietf.org/html/rfc7239]

Bumps to Feign 8.8.1

Change from @Autowired to context.getBean

Solves problems where FeignClientFactoryBean is run before auto-configuration.

fixed gh-441

Replaced incorrect @PathParameter with @PathVariable

* eureka-healthcheck:
  Eureka health check

Conflicts:
	.travis.yml