psychedelicious e76cc71e81 fix(config): edge cases in models.yaml migration
When running the configurator, the `legacy_models_conf_path` was stripped when saving the config file. Then the migration logic didn't fire correctly, and the custom models.yaml paths weren't migrated into the db.

- Rework the logic to migrate this path by adding it to the config object as a normal field that is not excluded from serialization.
- Rearrange the models.yaml migration logic to remove the legacy path after migrating, then write the config file. This way, the legacy path doesn't stick around.
- Move the schema version into the config object.
- Back up the config file before attempting migration.
- Add tests to cover this edge case
2024-03-19 09:24:28 +11:00
..
2024-03-19 09:24:28 +11:00
2024-03-19 09:24:28 +11:00
2024-03-01 10:42:33 +11:00
2024-03-06 21:57:41 -05:00
2024-03-01 10:42:33 +11:00
2024-03-01 10:42:33 +11:00