feat(database): add pushover notification type and related table

- Introduced a new notification type 'pushover' to the database.
- Created a new table 'pushover' with relevant fields for notification management.
- Updated the 'notification' table to include a foreign key reference to 'pushoverId' for enhanced notification handling.
- Added corresponding snapshot and journal entries to reflect these changes.

apps/dokploy/drizzle/0135_illegal_magik.sql

@@ -0,0 +1,12 @@
+ALTER TYPE "public"."notificationType" ADD VALUE 'pushover' BEFORE 'custom';--> statement-breakpoint
+CREATE TABLE "pushover" (
+	"pushoverId" text PRIMARY KEY NOT NULL,
+	"userKey" text NOT NULL,
+	"apiToken" text NOT NULL,
+	"priority" integer DEFAULT 0 NOT NULL,
+	"retry" integer,
+	"expire" integer
+);
+--> statement-breakpoint
+ALTER TABLE "notification" ADD COLUMN "pushoverId" text;--> statement-breakpoint
+ALTER TABLE "notification" ADD CONSTRAINT "notification_pushoverId_pushover_pushoverId_fk" FOREIGN KEY ("pushoverId") REFERENCES "public"."pushover"("pushoverId") ON DELETE cascade ON UPDATE no action;

apps/dokploy/drizzle/meta/_journal.json

@@ -960,6 +960,13 @@
       "when": 1769580434296,
       "tag": "0136_tidy_puff_adder",
       "breakpoints": true
+    },
+    {
+      "idx": 137,
+      "version": "7",
+      "when": 1770274109332,
+      "tag": "0137_colossal_sally_floyd",
+      "breakpoints": true
     }
   ]
 }