Summary

Fixes #3997

When a forward mapping uses a source path that includes the source parameter name (e.g. source.client.id), @InheritInverseConfiguration previously kept that prefix in the inverse target name (source.client.id). As a result, @Mapping(target = "client", ignore = true) on the inverse method did not match the nested inherited mapping, and MapStruct still created intermediate objects for ignored properties.

Root cause

1. copyForInverseInheritance swapped source/target naively, so source = "source.client.id" became inverse target = "source.client.id".
2. Code generation later strips the parameter prefix via TargetReference, so nested mapping still worked.
3. Ignore / redefinition matching runs earlier on the raw target name, where the first segment is the parameter name (source), not the property (client).

Fix

When building the inverse target name, strip the source parameter name prefix (e.g. source.client.id → client.id), mirroring SourceReference / TargetReference resolution. If the first segment is also a property of the source type, the full path is kept (property path takes precedence).

Tests

• Reproducer from the issue: nested sources with parameter prefix + inverse ignore = true → nested properties stay null
• Guard: same nested sources without ignores still reverse-map correctly

Checklist

• Provide test cases
• One pull request per feature/bug
• Meaningful history (single focused commit)
• Changelog entry in NEXT_RELEASE_CHANGELOG.md