Wip/bashscript refactoring

This is a major refactoring of the bash-script-creation parts. 

## Main Goals

- Reuse more bash scripts instead of copying around
- Try to consolidate rpm and debian script handling
- Separate `archetypes` and `standard` bash scripts

### Reusable bash snippets

To reuse more bash scripts every reusable part is stored inside the `linuxScriptReplacements`.
The `linuxScriptReplacements` are scoped, so we can provide some parts only for `Debian`
or `Rpm`. One of the default debian scripts now looks like this

```bash
${{header}}
${{control-functions}}

addGroup ${{daemon_group}}
addUser ${{daemon_user}} ${{daemon_group}} "${{app_name}} daemon-user" ${{daemon_shell}}

${{chown-paths}}
```

The `control-functions` define methods for user/group creation/deletion which work
on most linux distributions. 

### Consolidate rpm and debian

- For the `java_server` archetype the controlscripts are now name like the debian. See the _scriptlets-override-rpm_ test for details.
- Default bash scripts are now loaded via `<package>/<name>-template`, e.g. `debian/postinst-template`
- `DebianPlugin` has now less magic (like rpm). Only the `daemon_user` and `daemon_group` will be generated. The chown commands are now generated by `debianMakeChownReplacements` and added to the `linuxScriptReplacements in Debian`

### Archetype Bashscripts

Bash scripts for a specified archetype are now placed in `<archetype>/<package>/<script>-template`.
Non package-specified scripts are located in `<archetype>/<identifier>/<script>`. E.g

| Script        | Archetype    | Package  | Path                                                     |
| ------------- | --------------- | ------------ | ----------------------------------------------- |
| postinst     | java_server | debian      | java_server/debian/postinst-template |

For the `java_server` archetype we have different _systemloader_ scripts.
They get resolved like this

| Script        | ServerLoader    | Package  | Path                                               |
| ------------- | --------------- | ------------ | ----------------------------------------------- |
| start          | Upstart        | debian      | java_server/systemloader/upstart/start |

## Java Server Archetype

The scripts for the server archetype are now build up from basic templates.

- A server loader defines a `loader-functions` script which provides two functions `startService` and `stopService`
- Package specific scripts (rpm, debian) include the `loader-functions` with `${{loader-functions}}` (just a replacement) and can use these methods like the `control-script` functions

## Addition stuff

This won't be compatible with `0.7.x` as I started to use some sbt 0.13.x features.

## Tests and discussion

@jsuereth @kardapoltsev @aparkinson can you test on your systems? I have tested
everything so far on

- CentOS 6.5 (SystemV)
- Ubuntu 14.04 (Upstart)
I definitely like this idea a lot, splitting the template into re-usable components....

If only we could auto-document this stuff...