feat(memory): implement Dreaming consolidation flow

[JasonW404]

Summary

• add storage-independent SDK Dreaming models, REM analysis, OpenClaw-aligned scoring, gates, and stable selection
• add backend Light/REM/Deep orchestration, idempotent user-memory promotion, PostgreSQL advisory scope locking, and durable audit records
• expose manual run/audit APIs through config_service
• add idempotent migration/fresh-install SQL and restore Memory ORM mappings lost during target-branch conflict resolution
• repair target-branch import blockers required to load the config service

Verification

• 21 passed across Dreaming SDK, backend service, ASGI API, and schema-contract tests
• SDK Dreaming coverage: 98%
• backend Dreaming service coverage: 92%
• config service imports and registers /memory/dreaming/run and /memory/dreaming/audit

Known verification gap

AC-007 real PostgreSQL concurrent advisory-lock verification is not available in the current environment: no PostgreSQL connection variables are configured and the Docker daemon is inaccessible. Unit/service coverage verifies stable scope keys and lock-busy behavior, but this PR does not claim that as a substitute for the real two-connection PostgreSQL check.

Scope

This PR implements manual Dreaming only. Cron scheduling, watchdog/heartbeat, automatic archive execution, Dream Diary/LLM narrative generation, and a dedicated frontend Dreaming page remain out of scope.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.