Versioning of model

If models evolved a lot during the DA/DQ process, it may be useful to keep track of the history. This could follow a type of commit tracking.

see https://github.com/equinor/dot-archive/issues/177

> It would be useful to have a tracking of models in the tool to see which model was used previously. Then we can also see if a model changes which decision it might impact.

see https://github.com/equinor/dot-archive/issues/176

> - Add version control
> - log maybe on project edit page?

Start by reading the related requirements in dot-archive issues 177 and 176, especially the notes about tracking model history and project editing. Define how model versions should be recorded and how users can identify which previous model was used and whether a change affects decisions. The issue is complete when version history and its decision impact are specified and implemented in the tool.

Written by the indexing model from the issue text.