Fixes stalls in threaddump view due to not completing responses - only
reactive applications were affected so far.

If the build version of the instance is present in the metadata it's now
also considered and the version is now a attribute on the instance
itself. So when using non-boot application they can provide it via the
registration metadata.

- use MimeMessage with Content-Type text/hmtl
- use a single template for subject and body
- use a Spring aware TemplateResolver

The WebClient's responses should be always consumed, so that underlying
buffers are released.

Fixes #666

This commit enables client and server to work out of the box on
CloudFoundry.
The client derives the registration info (url and metadata) from the
VCAP environment variables.
The server computes a unique instanceId and the correct headers for the
cf router based on the metadata provided by instances. Also suppots the
CloudFoundry discovery client ootb.

closes #434

... to support multiple HttpHeadersProviders

fixes #647

closes #560

The info should be updated when the registration has changed. In order
to prevent a stale instance info, the sba client includes a "startup"
timestamp in the metadata as default. So when the instance is restarted
the registration changes and the info is updated, even when the instance
isn't considered as down in between.

To prevent this when using a discovery client you need to add a value
to the metadata which changes with every restart.
(e.g. `random=${random.value}`)

fixes #556