fix: resolve TypeScript errors in notification-bell and useRedeployDeployment

- Use Date type for notification createdAt/archivedAt (matches SDK)
- Pass empty object instead of undefined to queryKeyNotificationsUnreadCount
- Remove function wrapper around JSX in toast.success call

Co-Authored-By: Claude Opus 4.5 <[email protected]>

Author: simplesagar

client/dashboard/src/components/notification-bell.tsx

@@ -69,7 +69,7 @@ export function NotificationBell() {
       });
       queryClient.invalidateQueries({
         queryKey: queryKeyNotificationsUnreadCount(
-          lastViewedAt ? { since: new Date(lastViewedAt) } : undefined,
+          lastViewedAt ? { since: new Date(lastViewedAt) } : {},
         ),
       });
     },
@@ -149,8 +149,8 @@ interface Notification {
   level: string;
   title: string;
   message?: string | null;
-  createdAt: string;
-  archivedAt?: string | null;
+  createdAt: Date;
+  archivedAt?: Date | null;
 }
 
 interface NotificationListProps {
@@ -262,7 +262,7 @@ function NotificationItem({
             </Type>
           )}
           <Type small muted className="text-xs">
-            {formatDistanceToNow(new Date(notification.createdAt), {
+            {formatDistanceToNow(notification.createdAt, {
               addSuffix: true,
             })}
           </Type>

client/dashboard/src/pages/deployments/useRedeployDeployment.tsx

@@ -38,7 +38,7 @@ export const useRedeployDeployment = (
       const href = data.deployment?.id
         ? routes.deployments.deployment.href(data.deployment.id)
         : undefined;
-      toast.success(() => <RedeploySuccessToast href={href} />);
+      toast.success(<RedeploySuccessToast href={href} />);
       options?.onSuccess?.(data, vars, onMutateResult, ctx);
     },
     onError: (err, vars, onMutateResult, ctx) => {