Make migration log sorting smarter #12
Description
The migration log is going to cause processing issues when things are forced repeatedly. In a manual environment, this is not so bad, but it could be problematic for automated environments.
Have the migration log read in and processed. Log entries should be processed in applied_ts order. Versions that have an upgrade and downgrade action pairs should be eliminated from the final output. This will make the actual migration more pure for processing purposes since we want to track what is actually applied to the database as we manage downgrades
This issue directly relates to issue #8 for CI integration support.