Automatic migration

fixing AGPUSH-1075

There are some class warnings on startup, maybe we could disable these in the log4j settings. This seems a known issue https://liquibase.jira.com/browse/CORE-2024
not sure I fully understand this.  Why should this not fail on "error" ? 

Isn't it supposed to fail on errors that happen due to migration of _existing_ database content ?