Move Composio, logo.dev and Antigravity keys into Settings

The three third-party keys were hardcoded or read from the environment.
Operators now enter them in Settings > Integrations; they are stored
encrypted in the app-wide integration_keys table (migration 058).
An agent holding connector grants fails loudly when no Composio key is
saved. The goal-review test no longer depends on absolute dates.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

src/main/database/schema.ts

@@ -56,6 +56,7 @@ import { closeStaleWakeTasksSchema } from "./migrations/054-close-stale-wake-tas
 import { taskOriginSchema } from "./migrations/055-task-origin";
 import { kimiProvidersSchema } from "./migrations/056-kimi-providers";
 import { kimiCodeProviderSchema } from "./migrations/057-kimi-code-provider";
+import { integrationKeysSchema } from "./migrations/058-integration-keys";
 
 interface Migration {
   version: number;
@@ -121,6 +122,7 @@ const MIGRATIONS: Migration[] = [
   { version: 55, name: "task_origin", sql: taskOriginSchema },
   { version: 56, name: "kimi_providers", sql: kimiProvidersSchema },
   { version: 57, name: "kimi_code_provider", sql: kimiCodeProviderSchema },
+  { version: 58, name: "integration_keys", sql: integrationKeysSchema },
 ];
 
 const SCHEMA_VERSION = MIGRATIONS[MIGRATIONS.length - 1].version;