Create one log entry for every changed property instead of building a comma-separated summary

[Nicklas Nordborg]

This is related to #1784 and is a first step for making it possible to implement logging of old values. This is also related to #1753 and will make it easier to implement the requirement to ignore changes to AnnotationSet.itemId simply by annotating it with @NotLoggable (see #1785).

[Nicklas Nordborg]

(In [6349]) Fixes #1786: Create one log entry for every changed property instead of building a comma-separated summary

The old methods for generating change log entries in EntityDetails have been deprecated and replaced with new that can generate a list of change log entries instead. A list if of course only generated if the 'changelog.dblogger.detailed-properties' flag is enabled. Otherwise only a single entry is generated.

Also includes a cleaner fix for #1753 which now can take advantage of the @NotLoggable annotation created in #1785.

[Nicklas Nordborg]

(In [6510]) References #1786: Create one log entry for every changed property instead of building a comma-separated summary

Use ADD and REMOVE change type instead of CREATE/DELETE for changes that are not made on the main item. For example, when adding an annotation or data file to an item.