refactor: streamline notification header construction in sendNtfyNotification

- Consolidated header creation for the notification request, improving code readability and maintainability.
- Made the Authorization header conditional based on the presence of accessToken, enhancing flexibility.

Author: Mauricio Siu

packages/server/src/utils/notifications/utils.ts

@@ -156,20 +156,17 @@ export const sendNtfyNotification = async (
 	actions: string,
 	message: string,
 ) => {
-	const headers: Record<string, string> = {
-		"X-Priority": connection.priority?.toString() || "3",
-		"X-Title": title,
-		"X-Tags": tags,
-		"X-Actions": actions,
-	};
-
-	if (connection.accessToken) {
-		headers.Authorization = `Bearer ${connection.accessToken}`;
-	}
-
 	const response = await fetch(`${connection.serverUrl}/${connection.topic}`, {
 		method: "POST",
-		headers,
+		headers: {
+			...(connection.accessToken && {
+				Authorization: `Bearer ${connection.accessToken}`,
+			}),
+			"X-Priority": connection.priority?.toString() || "3",
+			"X-Title": title,
+			"X-Tags": tags,
+			"X-Actions": actions,
+		},
 		body: message,
 	});