With this change the AbstractNotifier isn't specialized on status changes, but
the default behaviour for the existing notifiers isn't changed.
In addition the existing notifiers have been improved so that subclassing has
become easier.
To have existing notifiers acting on other events you need to override
shouldNotify().

fixes #270

This adds a new FilteringNotifier which can use filters to suppres certain
events from being notified of. Two filter implementation are provided, one
filtering by name and one by id. Additional when a FilteringNotifier bean is
present, the autoconfiguration creates a REST-controller to add and remove
filters at runtime.

The RemindingNotifier sends periodic notifications using a delegate. It must be
added explicitly to the ApplicationContext

 * Use @EventListener instead of ApplicationListener-interface
 * Don't inherit ClientApplicationEvent from ApplicationEvent - so JournaledEvent isn't needed anymore
 * added eclipse formatter rules
 * reformatted all files

Added a simple event journal, jorunaling all ClientApplicationEvents using a simple, non-persistent store. So all information is lost after restart. Added corresponding view to UI.

* make sure non-UP applications are shown at the top of the list  (closes #55)
* refinements for health-section
* remove-button for all apps
* fixed headers in details view

using Gulp & Browserify
with a little help from https://blog.codecentric.de/en/2014/08/angularjs-browserify

* Separate AppStore from AppRegistry
* Allow Id generation to be altered
* Remove logic from Application; Move id genretation into AppRegistry
* Make AppStore threadSafe