VersionHandler can silently drop updates for incorrect input
The new VersionHandler
implemented in !11 (merged) can silently drop updates when the input was not correct according to biceps. When updating a child descriptor, it will trigger a version update of the parent. If the parent is updated by the user input afterwards, this update will get dropped without any warning. Since this is technically a violation of biceps, it should instead produce an error.
Implement a new preprocessing segment which checks the order of elements in description modifications such that parents are always updated before their children, as required by R5025. Same holds true for deletions through R5046. And reasonably for inserts as well, since inserting children before their parents makes no sense at all.