AT:

• engine-database-connection gets deployed with the cargo-maven-plugin using a war
• engine-database-connection is implemented as application instead of plugin

Note: We currently rely on docker operations done from our build that runs itself inside docker. This causes occasional hiccups and delays. In order for ops to provide engine/elasticsearch containers to be used during CI we need to get rid of engine-database-connection being installed as plugin. Deploying it as application allows us to start the engine beforehand from CI and deploy it using the cargo-maven-plugin