fix: scope postgres memory and reminder identity by tenant

[NeerajCodz]

Motivation

• The production PostgreSQL migration defined nextral_memories.id as a global PRIMARY KEY and nextral_reminders referenced memories and dedupe keys globally, enabling cross-tenant ID collisions and overwrite or denial-of-service.

Description

• Modify migrations/postgres/0001_core_schema.sql to make nextral_memories use a composite primary key PRIMARY KEY (tenant_id, id) while preserving the id column.
• Update nextral_reminders to reference memories with a tenant-scoped foreign key FOREIGN KEY (tenant_id, source_memory_id) REFERENCES nextral_memories(tenant_id, id).
• Replace global reminder deduplication with tenant-scoped uniqueness via UNIQUE (tenant_id, dedupe_key), keeping other columns and semantics unchanged.

Testing

• Existing project tests (cargo test) were run previously during validation and passed; the change is a schema-only migration and did not break the test suite.

---

Codex Task