without also ordering by migration_name, two migrations being applied at
the same time *can* (but won't always) result in the *earlier* migration
being returned as the latest one. as our migrations are not idempotent,
this causes the bot to crash on startup (and even if they *were*
idempotent, the code that inserts the new migration name into the
migrations table isn't)