Implement new scenario migration changelog

[thomas-qah]

To provide better insight into which scenarios are changed during data migrations, and in what way, we could set up a scenario migration changelog to keep track of these changes. A new changelog table should be made, containing a record for each scenario_migration that was performed, with the following data:

• Migration title
• Migration description to further explain the reasoning behind said migration
• Affected scenario IDs
• Affected inputs (name changes, removals, ...)
• Affected values (value changes due to new calculating methods, combinations of inputs, ...)

These records can then be used by scenarios to determine how compatible they still are.

We could wrap the changelog table records into a new model (ScenarioMigrationChangeLog or so) which should be accessible through the API. Some convenience methods may be added to this model, such as:

• affected_scenarios: Returns a collection of Scenarios that were altered during this migration

We could enrich the existing Scenario model with convenience methods as well, such as:

• migration_history: Returns a collection of ScenarioMigrationChangeLog objects which affected the given scenario
• backwards_compatible_until: gives the past date that the scenario is guarenteed to be compatible with

[github-actions[bot]]

This issue has had no activity for 60 days and will be closed in 7 days. Removing the "Stale" label or posting a comment will prevent it from being closed automatically. You can also add the "Pinned" label to ensure it isn't marked as stale in the future.

[github-actions[bot]]

This issue has had no activity for 60 days and will be closed in 7 days. Removing the "Stale" label or posting a comment will prevent it from being closed automatically. You can also add the "Pinned" label to ensure it isn't marked as stale in the future.