BUGFIX: Prevent augmenter from applying data of multiple nodes into the same element

[Sebobo]

What I did

This fixes a regression introduced in b56135a which removed the script tag, causing the augmenter to add the data of multiple nodes into the same html element in certain cases instead of adding an outer div. This lead to an error with the FlowQuery JavaScript API as it couldn't handle two nodepaths separated by a space as a single nodepath.

With this change the augmenter automatically adds an outer div if a node attribute appears twice. Therefore we have a single element for each wrapped node.

How to verify it

Create the following nodetype in the demo package:

NodeType:

Neos.Demo:Content.Test:
  ui:
    label: 'Test'
  superTypes:
    'Neos.Neos:Content': true
    'Neos.Demo:Constraint.Content.Main': true
  childNodes:
    test:
      type: 'Neos.Neos:ContentCollection'

Fusion prototype:

prototype(Neos.Demo:Content.Test) < prototype(Neos.Neos:ContentComponent) {
    renderer = afx`
        <Neos.Neos:ContentCollection nodePath="test"/>
    `
}

In 8.3.10 the rendered node in the backend would have two values in its context-path and fusion-path attributes and the FlowQuery endpoint throws an error when loading.

With the change the backend works fine again as in 8.3.9 and parent and child node are selectable.

[mhsdesign]

Thanks seems like the most clean and correct solution for this case.

[mhsdesign]

I cannot upmerge this fix to Neos 9 as the class was moved to Neos.Neos so this change has to be redone there!

[mhsdesign]

see neos/neos-development-collection#5278