fix: use named volume for ClickHouse to avoid permission issues in CI (#916)

The ClickHouse container was using a bind mount (./clickhouse-data) which creates
files with root ownership. When GitHub Actions' setup-python action scans the
workspace for pip caching, it fails with 'permission denied' on the clickhouse-data
directory.

This change switches to a named Docker volume (consistent with postgres and pgadmin),
which keeps the data in Docker's volume storage and avoids the permission issue.

Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-authored-by: Yosef Arbiv <yosef.arbiv@gmail.com>

Author: devin-ai-integration[bot]

integration_tests/docker-compose.yml

@@ -19,7 +19,7 @@ services:
       - "8123:8123"
       - "9000:9000"
     volumes:
-      - ./clickhouse-data:/var/lib/clickhouse
+      - clickhouse:/var/lib/clickhouse
     environment:
       CLICKHOUSE_DB: default
       CLICKHOUSE_USER: default
@@ -42,3 +42,4 @@ services:
 volumes:
   postgres:
   pgadmin:
+  clickhouse: