Order migrations by the second to avoid migration conflicts

[alexjustesen]

Description

This PR changes how migrations are published by ordering them by the current time's second. While not the ideal fix this does provide backwards safety as it only effects new installs.

Does this close any currently open issues?

Fixes #46

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Any relevant logs, error output, etc?

nope

...

Any other comments?

nope

...

Checklist

• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes