Optionally propagate metadata from masters to versions after file movement

[Arthur]

Currently if the users sets "Automatically propagate data from master to versions" this happens only under certain conditions. The conditions are:

1) There were external file changes in the directory containing the master and version or
2) The user changes the master's metadata or
3) The master's metadata is written back

If a version is created by moving a file that fulfills the master->version relationship into the masters directory inside IMatch, the file is marked as version but the automatic propagation does not happen. This is true for drag and drop and movements caused by the "Renamer". See "Img1".

The feature request is to add an option, which allows to propagate data from master to version also after a copy or a move operation inside IMatch. This option could be turned off by default to have no performance impact on existing databases/workflows. See "Img2".

This would allow to automatically inherit metadata from masters to versions after using the "Renamer" on huge file collections.