I removed the unecessary plugins from the build and reworked it to use
the ci friendly way of setting the version for releases (see
https://maven.apache.org/maven-ci-friendly.html).

This removes the spring-boot-starter-parent from the build, and
duplicates the necessary plugin configuration in he Spring Boot Admin'
parent instead. This way our BOM doesn't include version for
dependencies managed by boot's BOM

closes #299

The 1.4.0 release was a total disaster. Webpack didn't build the css correctly
because of travis using an ancient nodejs version.

With this commit the icons from FontAwesome are used. To achive this the
webpack css-loader is used and the location for the module.css has slightly
changed.
Also I removed the ugly sidebar (what a short life) and added a slim navbar at
the top for the detail views.

 - Updated Angular to 1.5.3
 - Removed Angular UI Bootstrap, to make the Angular update possible without
   updating Bootstrap
 - Moved every view into its own module
 - Added concatenation of the module js and css assets to the webserver
 - Created directives/components for the various visual components and trimmed
   down the controllers
 - Removed unecessary ngRoute
 - Removed classpath section in details (it is included in environment)
 - Moved the counters and gauges to a separated metrics view
 - Added target="_blank" for the logfile
 - Added information about version, loaded ui modules to the about page
 - Extracted the activiti view to a separate maven artifact

With this commit it is now possible to add your own ui modules to the servers
classpath and they will show up in the ui.
Every module needs an "entry" script file in the classpath located under
`META-INF/spring-boot-admin-server-ui/<modulename>/module.js`.
The module is be implemented as angular module and needs to be added to
the global `uiModules` list.
The spring-boot-admin-server-ui-activiti module is a simple sample for
adding a application view but it is also possible to add main-views.
Please have a look at the events module in spring-boot-admin-server-ui/modules.

Please note that the internals of the ui can change anytime.

I did an accidental release of a 1.3.2, so we need another increment

Cause it was often requested, now the context-path for the admin server is
configurable. This allows to move the admin-ui and endpoints to other http-
paths than "/".
NOTE: I'd still advise not to add the admin to the application you want to
monitor.

Remove unecessary dependencies

increment version