Fix EmbedsContentStreamAndNodeAggregateId interface for ESCR Events

[mhsdesign]

With adding the workspace name to the events #4996 we are now more and more relying on $event->workspaceName making this interface partly obsolete.

bastian said there:

[...] all events implementing EmbedsContentStreamAndNodeAggregateId are affected, so maybe it makes sense to extend (and rename) that interface

For example here we would like to use the workspace name:

neos-development-collection/Neos.Neos/Classes/Fusion/Cache/GraphProjectorCatchUpHookForCacheFlushing.php

Line 184 in 8796218

// FIXME: EventInterface->workspaceName

---

The EmbedsContentStreamAndNodeAggregateId interface is implemented 16 times.

Where its methods are nearly always implemented like:

public function getContentStreamId(): ContentStreamId
{
    return $this->contentStreamId;
}

public function getNodeAggregateId(): NodeAggregateId
{
    return $this->nodeAggregateId;
}

With one exception, the NodeReferencesWereSet doesnt have a nodeAggregateId property but its named sourceNodeAggregateId (unfortunately) -> to be fixed via #5153

---

But then again a bit of classification among the events would be great so we could easily allow them in canHandle when writing projections like we do already:

neos-development-collection/Neos.ContentRepository.Core/Classes/Projection/ContentStream/ContentStreamProjection.php

Line 167 in f00bce7

|| $event instanceof EmbedsContentStreamAndNodeAggregateId;

See slack discussion: https://neos-project.slack.com/archives/C04PYL8H3/p1711392719268439?thread_ts=1711353783.863809&cid=C04PYL8H3

So i would propose to add the workspace to the interface and rename it to something like EmbedsWorkspaceNameAndNodeAggregateId. Ideally we would also not have to introduce a new getter everywhere (getWorkspaceName) as this is a lot of boiler plate, and b opens the question wether to use $event->workspaceName directly or the getter.

With Php8.4 property hooks https://wiki.php.net/rfc/property-hooks we could write

interface EmbedsWorkspaceNameAndNodeAggregateId
{
    public WorkspaceName $workspaceName { get; }
    public ContentStreamId $contentStreamId { get; }
    public NodeAggregateId $nodeAggregateId { get; }
}

maybe we can use this already in a similar fashion leveraging phps @property and phpstan? But in that case we will stumble over that NodeReferencesWereSet as a anomaly and doesnt call it $nodeAggregateId -> to be fixed via #5153

/**
 * @property WorkspaceName $workspaceName
 * @property ContentStreamId $contentStreamId
 * @property NodeAggregateId $nodeAggregateId
 */
interface EmbedsWorkspaceNameAndNodeAggregateId
{
}