NodeType `references` followup

[mhsdesign]

With https://github.com/neos/neos-development-collection/pull/4677 a new syntax was introduced:

'My.Package:NodeWithReferences':
   references:
     singleReference:
       constraints:
         maxItems: 1
     multiReferences: {}

this issue tracks the open todos

• [x] support for showInCreationDialog: true https://github.com/neos/neos-ui/issues/3615? Should we still use the elements area with type: reference? Probably yes and we can be happy that elements as name was chosen to be more vague.
• [x] (re-)check all code like $nodeType->getProperties() or $nodeType->getConfiguration('properties.*')
• [x] keep reference editor configurable per dataTypes
• [ ] support magic i18n translation
• [ ] adjust nodetypes schema validation command
• [ ] adjust sebs ide json nodetypes schema
• [ ] followup: make sure constraints.nodeTypes works like ui.inspector.editorOptions.nodeTypes: ['My.Website:Author']
• [ ] document new syntax and features at docs neos
• [ ] adjust node.nodeType.properties in fusion (like rawcontent mode)
• [ ] default value support -> no to complex rather use node templates
• [ ] adjust Neos ui to properly understand references so its available via ClientEval:node.references
• [ ] write a migration (warning) for $nodeType->getPropertyType($foo) === 'references' -> $nodeType->hasReference($foo)
• [ ] write a migration / warning, when $nodeType->getProperties() is used or array merge with getReferences().
• [ ] copied from https://github.com/neos/neos-development-collection/issues/4549
  • [ ] Document the difference of q(node).property("reference") vs node.properties.reference because it causes confusion.
  • [ ] optionally discuss and implement point 1 & 2 from https://github.com/neos/neos-development-collection/issues/4549