feat: split ClickHouse into dual configurable databases (ja4_logs / ja4_processing)

Architecture:
- ja4_logs: raw log ingestion (http_logs_raw, http_logs, mv_http_logs)
- ja4_processing: analytics, aggregation, ML, dictionaries, audit

Configuration (env vars):
- CLICKHOUSE_DB_LOGS (default: ja4_logs)
- CLICKHOUSE_DB_PROCESSING (default: ja4_processing)

Changes:
- SQL migrations (10 files): all mabase_prod refs → ja4_logs or ja4_processing
  with correct cross-database references (MVs, views, dicts)
- deploy_schema.sh: substitutes DB names from env vars at deploy time
- Python shared settings: added CLICKHOUSE_DB_LOGS + CLICKHOUSE_DB_PROCESSING
- Dashboard routes (19 files): replaced ~80 hardcoded mabase_prod refs
  with settings.CLICKHOUSE_DB_LOGS / settings.CLICKHOUSE_DB_PROCESSING
- Bot-detector: DB → CLICKHOUSE_DB_PROCESSING, fetch_rules.py configurable
- Correlator: DSN example updated to ja4_logs
- Docker-compose + .env files: new env vars with defaults
- All documentation updated (14 markdown files)

All tests pass: sentinel 10/10, correlator 67.1%, bot-detector 11, dashboard 20, ja4_common 18

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

services/correlator/architecture.yml

@@ -533,7 +533,7 @@ schema:
 
 clickhouse_schema:
   strategy: external_ddls
-  database: mabase_prod
+  database: ja4_processing
   description: >
     La table ClickHouse est gérée en dehors du service. Le service insère dans une
     table RAW avec une seule colonne raw_json contenant le log corrélé complet
@@ -556,7 +556,7 @@ clickhouse_schema:
           type: DateTime
           default: now()
       insert_format: |
-        INSERT INTO mabase_prod.http_logs_raw (raw_json) VALUES
+        INSERT INTO ja4_processing.http_logs_raw (raw_json) VALUES
         ('{...log corrélé sérialisé en JSON...}')
       notes: >
         Le service utilise l'API native clickhouse-go/v2 (PrepareBatch + Append + Send).