Fix database migration for Redmine instances

Firstly, rake db:migrate doesn't work when rake is executed outside
of the rails project root. Write a custom db:absolute_migrate task that
works properly.

Also create a redmine_create_database bundle to explicitly force database
creation before we run rake db:absolute_migrate. Other ways of achieving
this effect I've tried:
  - setting a "database_created" class from databases promise (by using
    the classes => if_repaired("database_create") construct.
    + cf-promises accepts this, but a class is never set correctly.
  - using classes promise to set up the class explicitly based on a result
    of a command "psql --list |grep -q $(dbname)"
    + Doesn't work because psql --list has to be run as postgres user,
      and returnszero doesn't let us set the user.
  - Writing the same command as a module in the commands promise.
    + This one doesn't work because commands: is being executed once,
      before database is created and it's not being reexecuted at later
      passes.

The current solution isn't pretty, but it seems to be working correctly.
Make sure that the unicorn process for the instance is running