!!! TASK: Refactor `Node` property mapper to use new NodeAddress

[mhsdesign]

Solves: https://github.com/neos/neos-development-collection/issues/4873

This is an intermediate step after !!! FEATURE: Overhaul node uri building before we fully move to the new node address serialisation in the Neos Ui. Everything was refactored here that does not require adjustments in the Neos Ui (and the workspace module was also not really touched).

• avoid using the legacy node address instance in the code. The NodeAddressFactory is only used at the places where we still depend on the legacy format, but we create already new node address instances via createCoreNodeAddressFromLegacyUriString
• removed the $contentStreamId field from the legacy NodeAddress already (as we can otherwise not transform a new node address to this one). Also this prevents the $contentStreamId field from accidentally being used again in the migration time.
• removed the the unused legacy node address isInLiveWorkspace method.
• The currently unused method Neos.Node.serializedNodeAddress(node) will return the new node address format
• where previously Node $node was used to trigger property mapping (DataSourceController and WorkspaceController) we now pass the node as string and use the legacy node address factory to handle the legacy format manually. A followup will adjust everything to work with the new node address.
• the unused linkinservice will use the new node address string format if a string is passed as $node
• the Node property mappers were adjusted to use the new node address and not depend on the global active request handler
• lint Neos.Workspace.Ui/Classes with phpstan

Upgrade instructions

This change is breaking for existing Neos 9 users as the node being property mapped will require a new serialised input.

public function someAction(Node $node): {}

In Neos 8.3 you could call this action with the node like

?node=/sites/neosdemo/features/multiple-columns@user-admin;language=en_US

in Neos9-dev it was

?node=user-admin__eyJsYW5ndWFnZSI6ImVuX1VTIn0%3D__995c9174-ddd6-4d5c-cfc0-1ffc82184677

and now it must be the node address in json NodeAddress::toJson()

?node=%7B%22contentRepositoryId%22%3A%22default%22%2C%22workspaceName%22%3A%22live%22%2C%22dimensionSpacePoint%22%3A%7B%22language%22%3A%22es%22%2C%22country%22%3A%22ar%22%7D%2C%22aggregateId%22%3A%22node-1%22%7D

to build such a uri you can simply use:

$myActionUri = new Uri($this->uriBuilder->uriFor(...));
$myActionUriWithNode = UriHelper::uriWithAdditionalQueryParameters(
    $myActionUri,
    ['node' => NodeAddress::fromNode($node)->toJson()]
);

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]

Okay in that case id merge it ;)