File system connector should behave better when creating "jcr:content" child nodes under an "nt:file" node with the default conflict behavior

When using the Graph API to create file nodes in a file system source, the connector does not behave as one would expect when a "jcr:content" child node is being created under an "nt:file" node, and when the default node conflict behavior of "append" is used. This is because the "jcr:content" node is actually created automatically as part of the creation of the "nt:file" node, so when the connector processes the request to create the "jcr:content" node (using the default "append" conflict behavior), a "jcr:content" node already exists and the connector does not support same-name-siblings.

IMO, the connector should behave better, since the "nt:file" node type only allows on "jcr:content" child anyway.