Preserve live Kamal accessory bind paths

[ewlarson]

Summary

• restore the relative Kamal accessory directory sources that resolve to the existing production binds
• add a focused regression test and transfer-readiness assertions for those directory identities
• correct the deployment and repository-transfer runbooks with live preflight evidence

Why

The change-window preflight found that the running PostgreSQL, Elasticsearch, and Redis accessories still use Kamal-resolved paths under /home/ewlarson/ogm-api-, while develop named new /var/lib/opengeometadata-api/ sources. An accessory reboot with that configuration could mount different, empty directories.

Validation

• ./scripts/verify_transfer_readiness.sh
• focused Kamal configuration test: 2 passed, 1 skipped
• read-only live mount, image-digest, container-health, registry-access, and API checks
• current PostgreSQL custom-format backup completed and passed pg_restore catalog validation

Operational scope

This PR does not deploy, restart accessories, change the production image, rewrite Git history, delete branches, or transfer the repository. The cutover remains paused until this correction is reviewed and merged.