Fix #12085: regression tests for version inheritance from remote parent

[gnodet]

Summary

• Add regression tests verifying that version inheritance from remote parent POMs works correctly in both single-project and multi-module builds
• The issue (Invalid Collect Request: null root artifact for projects inheriting version from remote parent #12085) reported Invalid Collect Request: null when building projects that inherit version from a remote parent POM with <relativePath/>
• Investigation confirmed the root cause was uninterpolated repository expressions from parent POMs leaking to the CollectRequest validator — already fixed by Filter transitive repositories with uninterpolated IDs #12050 (9332ad3) and cee3c33 (Profile-scoped properties not interpolated in repository URL in Maven 4 (rc5) #11920)
• The "null" in the error message was from CollectRequest.toString() (always shows null for getRoot() since Maven uses getRootArtifact()), not from a null root artifact

Test plan

• testVersionInheritedFromRemoteParent — single-project build inheriting version from remote parent with different groupId
• testVersionInheritedFromRemoteParentMultiModule — multi-module build with child inheriting version from remote parent
• Both tests verify: version inherited correctly, artifact non-null, artifact version matches, groupId from child POM
• Test parent POM includes profile with uninterpolated repository expressions to verify filtering

🤖 Generated with Claude Code

[github-actions]

@gnodet Please assign appropriate label to PR according to the type of change.