Fix relocation stub: add parent so it can actually be signed+published

[bernardladenthin]

Summary

• The llamacpp-ai-index-maven-plugin relocation-stub module (from the previously-merged srcmorph: extract core+CLI, rename plugin, bump to 1.1.0, fix reactor CI #144) had no <parent>, so it inherited neither the release profile's maven-gpg-plugin signing execution nor its central-publishing-maven-plugin binding. Running the real mvn -P release deploy would have hit this module with nothing configured to sign or publish it — no <distributionManagement><repository> either — falling through to the plain Super-POM maven-deploy-plugin:deploy binding for pom packaging, which needs an explicit deployment repository this file correctly doesn't declare. That would fail the whole reactor deploy the moment it reached this module (or at best leave the relocation POM never actually published, defeating its purpose).
• Fix: add <parent>srcmorph-parent</parent> while keeping this module's own explicit <version>1.0.4</version> as a deliberate override — Maven fully supports a child pinning a different version than its parent; only omitting <version> inherits the parent's.

Test plan

• Effective POM under -P release now shows both maven-gpg-plugin and central-publishing-maven-plugin bound for this module (previously absent even with -P release explicitly passed)
• Effective POM's own <version> still resolves to 1.0.4 (not clobbered to the parent's 1.1.0)
• <distributionManagement><relocation> unchanged — still points at net.ladenthin:srcmorph-maven-plugin:1.1.0
• Re-tested mvn versions:set -DnewVersion=X -Dexcludes=net.ladenthin:llamacpp-ai-index-maven-plugin in a scratch copy — the stub's version correctly stays pinned while the rest of the reactor bumps, confirming the existing exclusion guidance still works with the new <parent> in place
• mvn clean verify from repo root — BUILD SUCCESS
• CI green on this branch (pending)

Related issues / PRs

Follow-up to #144 (merged) — this closes a gap discovered while double-checking release-readiness after that merge.

Checklist

• I have read CONTRIBUTING.md and CODE_OF_CONDUCT.md
• My commits follow Conventional Commits
• No security-sensitive changes

---

Generated by Claude Code