9.0 !!! REFACTOR: adjust move event structure (breaking event payload change)

[skurfuerst]

ToDo List

• Event Payload Update
• Command Handler Update
• Projection Update
• Event Documentation
• tests run through again
• adjust DocumentUriPathProjection
• adjust ChangeProjection

The current structure of the NodeAggregateWasMoved is rather complex. Especially the NodeMoveMappings are hard to grasp.

Besides, the hash of the affected ContentDimensionSpacepoints is expected as keys for NodeVariantAssignments::createFromArray() which makes this error prone. Also it makes the internal implementation detail part of the event payload.

Solution

It makes sense to combine the two sets newParentAssignments and newSucceedingSiblingAssignments into one and to replace the associative array, e.g.:

OLD:

{
	"nodeAggregateIdentifier": "a",
	"nodeMoveMappings": [{
		"movedNodeOrigin": {
			"language": "ch"
		},
		"newParentAssignments": {
			"1041cc1fe1030c1a82ac24346f8c69a7": {
				"nodeAggregateIdentifier": "b",
				"originDimensionSpacePoint": {
					"language": "de"
				}
			}
		},
		"newSucceedingSiblingAssignments": {
			"1041cc1fe1030c1a82ac24346f8c69a7": {
				"nodeAggregateIdentifier": "b1",
				"originDimensionSpacePoint": {
					"language": "de"
				}
			}
		}
	}],
        // ...
}

New:

{
	"nodeAggregateIdentifier": "a",
	"nodeMoveMappings": [{
		"movedNodeOrigin": {
			"language": "ch"
		},
		"newLocations": [{
			"coveredDimensionSpacePoint": {
				"language": "ch"
			},
			"newParent": {
				"nodeAggregateIdentifier": "b",
				"originDimensionSpacePoint": {
					"language": "de"
				}
			},
			"newSucceedingSibling": {
				"nodeAggregateIdentifier": "b1",
				"originDimensionSpacePoint": {
					"language": "de"
				}
			}
		}]
	}],
        // ...
}

Resolves: #3825