FEATURE: Create node template definition yaml dump from node subtree

[mhsdesign]

flow nodeTemplate:createFromNodeSubtree <nodeIdentifier>

closes: #37

also adds a first near-e2e test ;) #33

when creating a more complex node template, to create multiple pages and content elements, it can be helpful to take the current node subtree as reference. For this case a command controller would be great.

flow nodeTemplate:createFromNodeSubtree 136a646c-b2d5-4475-8e24-b25727aa7913 --workspaceName=live

Your.NodeType:
  options:
    template:
      childNodes:
        page0:
          name: page-0
          type: Foo.Bar:Page
          properties:
            title: 'my page'
            uriPathSegment: my-page
            # someReference -> Reference of NodeTypes (Neos.Neos:Document) with value Node(13f5e86b-7b0e-4a7f-9a8a-af6bdf1c1913)
          childNodes:
            page0:
              name: page-0
              type: Foo.Bar:Pag
              properties: ...
              childNodes:
                 mainContentCollection:
                   name: main
                   childNodes: ...

[Sebobo]

Great change, left some comments

[Sebobo]

Works great ❤️ but can you add instructions to the readme?

[lorenzulrich]

Thanks, great work!

[lorenzulrich]

For my taste, a command name should contain a verb, e.g. createConfigurationForSubtree. Furthermore, "Subtree" is a term that is not really known to integrators. In Docs and ReadTheDocs, there are three mentions of this term (one of the referring to Git subtree), so I suggest to use a more common term.
Idea: dumpConfigurationForNodeTree

[mhsdesign]

Hi thanks for your review. The naming subtree is taken from the new ESCR, where you can actually get with one sql query the whole subtree:

ContentSubgraphInterface::findSubtree

A subtree will look like this

so i like to keep the name subtree (maybe we can add the prefix node so people understand its node releated?: NodeSubtree)

but i agree that something like a verb could also be a nice addition to the command name:

# original
flow nodeTemplate:fromSubtree <nodeIdentifier>

# your proposal
flow nodeTemplate:createConfigurationForSubtree <nodeIdentifier>

# your other proposal
flow nodeTemplate:dumpConfigurationForNodeTree <nodeIdentifier>

# my idea:
flow nodeTemplate:createFromNodeSubtree <nodeIdentifier>

@Sebobo and me decided for now on nodeTemplate:createFromNodeSubtree