When running the db command do not start server directly after.

When the db command is run, Ursus will attempt to start the server after the db command has completed. Unfortunately the difference in the number of args between the "server" and "db" command will result in an exception. Ursus will think you passed a null configuration file for the "server" command and will attempt to use the configuration file name based on the class name.

It is also unexpected behavior to start the server when the intention is to simply run the db command. This db command will now only run the liquibase command and exit.