In order to do a relaease not waiting for Spring Cloud
Finchley.REALEASE move all depedent stuff into a seperate module which
can be excluded during build

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

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 avoid some strange config sorting errors using the
DeferredImportSelector, switch to a real AutoConfiguration activated by
a marker bean

Use the metadata for health-/managament-url in the default service conversion.
This allows custom health- and management-path per application.

fixes #205

Update to Spring Cloud Brixton and add the concept of ServiceInstanceConverters.
A ServiceConverter is used to convert discovered ServiceInstances to
Applications. The old converter and one for Eureka is provided. It is also
possible to provide your own implementation.

closes #154

Streamline the Hazelcast support with boot 1.3 and support storing events in hazelcast

closes #113

The mail notification is enabled if a mailSender is present specified via spring.mail.* properties.
On default the mail is sent to root@localhost and the chages from UNKNOWN to UP are ignored.

The health-check is made at a fixed interval (default: 10s) for all expired status-information (default-lifetime: 30s).
The application health-endpoint must either respond with a JSON-Body having a status-field or with an empty body and all 2xx-http-responses are interpreted as UP and every other status as DOWN.