BUGFIX: nodetypes:// normalize the path to unix

[mhsdesign]

as nodetypes://Foo.Bar\SomeFile.bar might be requested on windows, and we split later on unix slash /

resolves: #4358 in combination with #4359

Upgrade instructions

Review instructions

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

[dlubitz]

I don't get, why you should fix a wrong "nodetype://" path here. Shouldn't we fix where that got wrongly built?

[mhsdesign]

The RecursiveIteratorIterator in the FilePatternResolver builds them invalid / in windows style

[mhsdesign]

but thx @dlubitz for setting the bar high ;) I just found FilesystemIterator::UNIX_PATHS which might do as well. And even better ^^

[mhsdesign]

Yes the flag works as expected ;)

@dlubitz what do you say - should we also use the flag here neos/flow-development-collection#3088?

[dlubitz]

I'm not that deep in this, but this is a different thing, isn't it?
In findComposerPackagesInPath you need the windows-formated path for iterating the recursive (L636) and just the return of findComposerPackagesInPath would be in Unix-style. Writing that raises the question... WHY?