Parent-child transformations should consider the "push annotations" flag

[Nicklas Nordborg]

The "push annotations" flag was introduced in #1605 and allows a child item to switch directions when finding parent items. For example:

  A
 B C
 D
 E

From E, the immediate parent items are D, B and A. C can also be considered a parent item if it has a subtype with the "push annotations" flag set, which allows E to inherit annotations from it.

However, the "Item list" functionality has not considered the "push annotations" flag, making it impossible to "Find parent items of type C" without using an intermediate item list at the A level.

So, if an item list is using a synchronization filter were items of type C are included it would be nice if it could automatically check the "push annotations" flag and understand that it should load parent items of type A and before moving down to child items.

[Nicklas Nordborg]

In 7772:

References #2203: Parent-child transformations should consider the "push annotations" flag

This should now be implemented via the PushToParentsTransformer implementation. Note that this transformer is only added to the first step and move up as long as it finds items that has the "push annotations" flag set.