Fresh platform should not apply migrations #445
Description
Problem to Solve
Today every users starting a new platform could have some error logs due to migrations that should not be applied. Its not really a problem but its confusing. We need to improve the migration proces to split the init phase and rely on the last migration date to know if we need to play migrations or not
Current Workaround
No
Proposed Solution
- Move the 2 firsts migrations to the init phase of the platform.
- Change migration code to support a status without migration
- At fresh start, no migration must be played
- With an existing platform, check the migration status date to apply only new migrations