feat: Add 'ntfy' notification type and related database schema changes

- Introduced a new notification type 'ntfy' to the public.notificationType enum.
- Created a new table 'ntfy' with fields for notification ID, server URL, topic, access token, and priority.
- Updated the existing 'notification' table to include a foreign key reference to the new 'ntfy' table.

apps/dokploy/drizzle/0110_red_psynapse.sql

@@ -0,0 +1,11 @@
+ALTER TYPE "public"."notificationType" ADD VALUE 'ntfy';--> statement-breakpoint
+CREATE TABLE "ntfy" (
+	"ntfyId" text PRIMARY KEY NOT NULL,
+	"serverUrl" text NOT NULL,
+	"topic" text NOT NULL,
+	"accessToken" text NOT NULL,
+	"priority" integer DEFAULT 3 NOT NULL
+);
+--> statement-breakpoint
+ALTER TABLE "notification" ADD COLUMN "ntfyId" text;--> statement-breakpoint
+ALTER TABLE "notification" ADD CONSTRAINT "notification_ntfyId_ntfy_ntfyId_fk" FOREIGN KEY ("ntfyId") REFERENCES "public"."ntfy"("ntfyId") ON DELETE cascade ON UPDATE no action;

apps/dokploy/drizzle/meta/_journal.json

@@ -771,6 +771,13 @@
       "when": 1757052053574,
       "tag": "0109_remarkable_sauron",
       "breakpoints": true
+    },
+    {
+      "idx": 110,
+      "version": "7",
+      "when": 1757189541734,
+      "tag": "0110_red_psynapse",
+      "breakpoints": true
     }
   ]
 }