fix(compose): fix volume mount for postgres for PG18

[jsell-rh]

Summary by CodeRabbit

Chores

• Updated Docker Compose configuration for PostgreSQL database services. The data storage volume mount has been repositioned to optimize how database data is persisted across container restarts and redeployments. This infrastructure adjustment ensures more reliable data preservation in deployment environments.

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

Walkthrough

Updated the Docker Compose compose.yaml file to modify the PostgreSQL service's volume mount configuration. The named volume postgres_data is now mounted to /var/lib/postgresql instead of /var/lib/postgresql/data, changing the internal container path where database files are persisted.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies a specific fix to the Docker Compose postgres service volume mount configuration related to PostgreSQL 18, matching the actual changeset which modifies the volume mount path.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/update-container-images

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}