fix(warden): add retry queue for failed authorization tuple writes

Project ownership tuples were silently dropped when Warden was
unavailable. Add a DB-backed retry queue with exponential backoff
to ensure tuples are eventually written.

Author: coopbri

src/generated/drizzle/0012_neat_fallen_one.sql

@@ -0,0 +1,12 @@
+CREATE TABLE "warden_sync_queue" (
+	"id" uuid PRIMARY KEY DEFAULT gen_random_uuid() NOT NULL,
+	"operation" text NOT NULL,
+	"payload" jsonb NOT NULL,
+	"attempts" integer DEFAULT 0 NOT NULL,
+	"max_attempts" integer DEFAULT 10 NOT NULL,
+	"last_error" text,
+	"next_retry_at" timestamp(6) with time zone DEFAULT now() NOT NULL,
+	"created_at" timestamp(6) with time zone DEFAULT now() NOT NULL
+);
+--> statement-breakpoint
+CREATE INDEX "warden_sync_queue_next_retry_idx" ON "warden_sync_queue" USING btree ("next_retry_at");