fix(jobs): gate lifecycle-email cron behind prod-host check

dev.sase.tr was running the daily lifecycle-email cron (trial-ending,
win-back) against sase_dev, which is a seeded copy of the prod DB —
real customers were getting duplicate mails (one from prod, one from
dev). Mirror the isCatalogBackfillEnabled() gate so the lifecycle cron
only registers on the canonical prod host (COOLIFY_FQDN=sase.tr or
BETTER_AUTH_URL=https://sase.tr). LIFECYCLE_EMAIL_ENABLED env can force-
enable for staging testing. The else branch removes any stale scheduler
from Redis so a previously-registered cron stops firing.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

apps/api/src/jobs/prefetch-utils.ts

@@ -18,6 +18,23 @@ export function isCatalogBackfillEnabled(): boolean {
   );
 }
 
+/**
+ * True ONLY on the real production deployment (sase.tr).
+ *
+ * Same rationale as {@link isCatalogBackfillEnabled} — both prod and dev run
+ * with `NODE_ENV=production`, so we gate on the prod host. Without this gate
+ * the dev deploy would send duplicate trial-ending / win-back e-mails to real
+ * users (sase_dev DB is a copy of prod data). An explicit
+ * `LIFECYCLE_EMAIL_ENABLED` env wins (e.g. to force-test on staging).
+ */
+export function isLifecycleEmailEnabled(): boolean {
+  const flag = process.env.LIFECYCLE_EMAIL_ENABLED;
+  if (flag != null && flag !== "") return flag === "true";
+  return (
+    process.env.COOLIFY_FQDN === "sase.tr" || process.env.BETTER_AUTH_URL === "https://sase.tr"
+  );
+}
+
 /**
  * Signals the worker that this job is rate-limited and should be deferred.
  *