Migrations do not give sufficient information about error cases

[sgrif]

I'm unsure if we ever actually expect migration failures to be handled. Perhaps we should actually be unwraping from these functions. If not, we need to make sure our errors have sufficient information to be useful without a stacktrace, and not: QueryError(DatabaseError("near \"(\": syntax error"))

[sgrif]

Today our output looks like this:

We should be able to assume that errors will only occur because of a bad connection, or an error running a specific migration. It's clear in the output when a connection error occurred (though the output could be better here), and when an error occurs running a migration, it immediately follows the migration version. I'm not sure that there's much else we can do here.