Ensure bin/setup works

[stevepolitodesign]

Closes #1224

It's unclear why we need to run migrations, since we're already calling
db:prepare which does the following:

If the database exists but the tables have not been created, the
command will load the schema, run any pending migrations, dump the
updated schema, and finally load the seed data. See the Seeding Data
documentation for more details.

However, I found that calling db:migrate in the application template
worked.

[stevepolitodesign]

This might need more work.

bin/rails aborted!
ActiveRecord::NoDatabaseError: We could not find your database: app_name_development. Available database configurations can be found in config/database.yml. (ActiveRecord::NoDatabaseError)

To resolve this error:

- Did you not create the database, or did you delete it? To create the database, run:

    bin/rails db:create

- Has the database name changed? Verify that config/database.yml contains the correct database name.


Caused by:
PG::ConnectionBad: connection to server on socket "/tmp/.s.PGSQL.5432" failed: FATAL:  database "app_name_development" does not exist (PG::ConnectionBad)

I might need to call both?