dev and production config files generated with `pubsweet new`
Running pubsweet new
generates both a production and dev config, but only the db corresponding to the production/dev mode. This leads to a scenario where an app can be generated with both production and dev DBs, but the secret of one of the configs will not match the data stored in the DB.
Solution:
pubsweet new
should only generate the config file corresponding to the production/dev mode of the command.