Task/centralise rebaseable command enrich with command

[mhsdesign]

FYI the essence is in 76a975d

<?php

declare(strict_types=1);

namespace Neos\ContentRepository\Core\CommandHandler;

use Neos\ContentRepository\Core\Feature\Common\RebasableToOtherWorkspaceInterface;

/**
 * Optional interface for all content repository command serializer
 *
 * See {@see RebasableToOtherWorkspaceInterface} for more details regarding serialized commands.
 *
 * @internal no public API, because commands are no extension points of the CR
 */
interface CommandSerializerInterface
{
    public function canSerialize(CommandInterface $command): bool;

    public function serialize(CommandInterface $command, CommandHandlingDependencies $commandHandlingDependencies): RebasableToOtherWorkspaceInterface;
}

#5301 (comment)

Alright, at least according to the tests this works now. I also went through all Rebasable commands to check if the events get enriched. the Dimension ones were the only missing. IMHO we should centralize this behavior, I opted against doing it here though as I think we need to consider if there would have to be any more logic involved to decide what gets enriched with commands, in what way, when we override the command if there is already metadata and finally what the causation ids are. I guess we could ignore all these questions and centralize it, but it warrants a closer look and is therefore out of scope of this change.

Upgrade instructions

Review instructions

Checklist

• Code follows the PSR-2 coding style
• Tests have been created, run and adjusted as needed
• The PR is created against the lowest maintained branch
• Reviewer - PR Title is brief but complete and starts with FEATURE|TASK|BUGFIX
• Reviewer - The first section explains the change briefly for change-logs
• Reviewer - Breaking Changes are marked with !!! and have upgrade-instructions

[mhsdesign]

I found a flaw with CreateRootNodeAggregateWithNode and ChangeNodeAggregateType, as they dont have serialized counterparts, but still require their TetheredDescendantNodeAggregateIds to be precalculated, so we would have to pass them too through the CommandSerializerInterface:

neos-development-collection/Neos.ContentRepository.Core/Classes/Feature/RootNodeCreation/RootNodeHandling.php

Lines 93 to 95 in 76a975d

	// Write the auto-created descendant node aggregate ids back to the command;
	// so that when rebasing the command, it stays fully deterministic.
	$command = $command->withTetheredDescendantNodeAggregateIds($descendantNodeAggregateIds);

That would make the API in

public function canSerialize(CommandInterface $command): bool;

public function serialize(CommandInterface $command, CommandHandlingDependencies $commandHandlingDependencies): RebasableToOtherWorkspaceInterface;

less tidy because we need to allow CommandInterface|RebasableToOtherWorkspaceInterface everywhere.

[mhsdesign]

We discussed that centralising the enrichment would be cool, but its also just making "wrong" things pretty :D
Instead we should strive in the long run to possibly reconstruct the commands from the events or just apply the events with constraint checks and let those fail.
For that reason ill dump my CommandSerializerInterface idea!

(see #5348)