feat: add resend notification functionality

- Introduced a new notification type "resend" to the system.
- Added database schema for resend notifications including fields for apiKey, fromAddress, and toAddress.
- Implemented functions to create, update, and send resend notifications.
- Updated notification router to handle resend notifications with appropriate API endpoints.
- Enhanced existing notification services to support sending notifications via the Resend service.
- Modified various notification utilities to accommodate the new resend functionality.

schema.dbml

@@ -69,6 +69,7 @@ enum notificationType {
   telegram
   discord
   email
+  resend
   gotify
   ntfy
   custom
@@ -455,6 +456,13 @@ table email {
   toAddress text[] [not null]
 }
 
+table resend {
+  resendId text [pk, not null]
+  apiKey text [not null]
+  fromAddress text [not null]
+  toAddress text[] [not null]
+}
+
 table environment {
   environmentId text [pk, not null]
   name text [not null]
@@ -691,6 +699,7 @@ table notification {
   telegramId text
   discordId text
   emailId text
+  resendId text
   gotifyId text
   ntfyId text
   customId text
@@ -1133,6 +1142,8 @@ ref: notification.discordId - discord.discordId
 
 ref: notification.emailId - email.emailId
 
+ref: notification.resendId - resend.resendId
+
 ref: notification.gotifyId - gotify.gotifyId
 
 ref: notification.ntfyId - ntfy.ntfyId
@@ -1191,4 +1202,4 @@ ref: volume_backup.redisId - redis.redisId
 
 ref: volume_backup.composeId - compose.composeId
 
-ref: volume_backup.destinationId - destination.destinationId
+ref: volume_backup.destinationId - destination.destinationId