Resolves #505: getReactorModels using correct module paths when the module name includes pom.xml

[andrzejj0]

Nothing fancy or spectacular, just a simple bug fix for the edge case of having the module name include the pom.xml file path. In the unpatched implementation, the "/pom.xml" was treated as part of the directory name when descending down the module tree to retrieve child models... Fixed that.

Added some tests (unit test for the PomHelper method + integration test for the use case from the issue).

@slawekjaranowski please review

[andrzejj0]

getProjectParent( final ModifiedPomXMLEventReader pom, VersionsHelper helper ) and removeMissingChildModules( Log logger, MavenProject project, Collection<String> childModules ) were no longer used -> removed

[andrzejj0]

Rebased.

[rshkv]

I think there might have been a break here: versions:set stopped working in my repo and I narrowed it down to this commit. I'm attaching --debug logs for a run with this commit and a run on 2.13.0.

versions-set-output-2.13.0.txt
versions-set-output-805.txt

[slawekjaranowski]

please follow #848 #849

[andrzejj0]

@rshkv thanks. Tested this with the PR, problem looks solved.

[rshkv]

Thank you for the reply guys!