Change CopyNodesRecursively command to capture intent

[bwaidelich]

Currently the CopyNodesRecursively command has two properties that reflect the inner working more than the original intention to copy existing nodes.
This is a problem because it allows to circumvent constraint checks.

Namely:

• $nodeTreeToInsert that basically contains a serialized snapshot of all the affected nodes
• $nodeAggregateIdMapping that creates new, random, node aggregate ids

Both should not happen at command creation time but in the command handler, i.e. we should introduce some CopyNodesRecursivelySerialized variants.

Related: #5353

[mhsdesign]

More importantly this will allow us to do proper constraint checks (see

neos-development-collection/Neos.ContentRepository.Core/Classes/Feature/NodeDuplication/Dto/NodeSubtreeSnapshot.php

Lines 63 to 64 in ed9efe3

	// we assume here that the child node is tethered because the grandparent specifies that.
	// this is not always fully correct and we could loosen the constraint by checking the node type schema

for example)

And further this is required for copying with dimensions: #5054

[bwaidelich]

More importantly this will allow us to do proper constraint checks

Right, that's why they are mentioned in the 2nd phrase :)