BUGFIX: Translate label for childNodes

[bijusk]

Added translation support for labels of autocreated childNodes

Example:

yaml-File:

'Neos.Demo:Content.Columns.Two':
  ...
  childNodes:
    column0:
      type: 'Neos.Demo:Collection.Content.Column'
      label: i18n
    column1:
      type: 'Neos.Demo:Collection.Content.Column'
      label: i18n

xlf-file:

...
<trans-unit id="childNodes.column0" xml:space="preserve">
	<source>Left Column</source>
</trans-unit>
<trans-unit id="childNodes.column1" xml:space="preserve">
	<source>Right Column</source>
</trans-unit>
...

Changes:

Added childNode labels in addLabelsToNodeTypeConfiguration in NodeConfigurationEnrichmentAspect and implemented function for transforming i18n to a later translated id

Implemented translating of said id to the actual translation in ExpressionBasedNodeLabelGenerator in function getLabel

resolved: #5643

Environment

- Flow: 8.4
- Neos: 8.4
- PHP: 8.3

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

[Sebobo]

Thx, works great. Just one small change necessary, which basically everyone forgets when doing something with nodetype configs ;)

[Sebobo]

Suggested change

	if ($this->shouldFetchTranslation($childNodeConfiguration)) {
	if ($childNodeConfiguration && $this->shouldFetchTranslation($childNodeConfiguration)) {

Nodetype settings are always nullable in subtypes f.e.. So we always have to catch this case. Currently this would lead to an exception and make it impossible to overwrite a child node from a subtype.

[bijusk]

Thx for catching this! Comitted a fix where I also removed an unnecessary function argument

[Sebobo]

Looks good now, thx!

[dlubitz]

Thank you very much. Looks good by reading. I left two suggestions to make it more type safe.