port: feat(notifications): allow SMTP without authentication (upstream #4844)

[AminDhouib]

Ports upstream Dokploy/dokploy#4844 by @hbilal9 into the fork (upstream closes Dokploy#4842).

Problem

Some SMTP relays (e.g. Google SMTP Relay with IP allowlisting) do not use username/password authentication, but the email notification form and API required both, and sendEmailNotification always passed auth: { user, pass } to nodemailer.

Fix (from upstream, applied verbatim)

• handle-notifications.tsx: form notificationSchema makes username/password optional, the fields show an "Optional. Leave blank if your SMTP server does not require authentication." description and a null-safe value, and the create/test payloads coerce to data.username || "".
• packages/server/src/db/schema/notification.ts: the apiCreateEmail zod schema relaxes username/password from z.string().min(1) to z.string().
• packages/server/src/utils/notifications/utils.ts: nodemailer only receives auth when both credentials are present (...(username && password ? { auth } : {})).

Migration (fork addition beyond upstream)

Upstream keeps the email table's username/password columns NOT NULL and relies on empty-string coercion. This fork goes further so the schema faithfully represents credential-less relays:

• Drops .notNull() on email.username / email.password in the drizzle schema.
• Adds migration 0192_futuristic_texas_twister.sql in the next free journal slot after 0191 (idx 192, when strictly greater than the previous entry), LF line endings per .gitattributes. It is additive-relaxing and idempotent:

  ALTER TABLE "email" ALTER COLUMN "username" DROP NOT NULL;
  ALTER TABLE "email" ALTER COLUMN "password" DROP NOT NULL;

• Meta _journal.json + 0192_snapshot.json regenerated by drizzle-kit generate (no unrelated drift — only the two DROP NOT NULL statements).
• Because the loaded email type is now nullable, the edit form coerces notification.email?.username/password to undefined when resetting.

Adaptation

Added a small self-contained unit test (__test__/notifications/email-auth.test.ts, authored separately) asserting auth is included only when both credentials are non-empty (empty/undefined/partial cases covered), following the fork's existing contract-mirroring test pattern. Upstream shipped no test.

Verification

• pnpm --filter=dokploy typecheck and pnpm --filter=@dokploy/server typecheck — both clean.
• pnpm exec vitest __test__/notifications/email-auth.test.ts --run — 5 passed.
• Migration generated via drizzle-kit generate; snapshot/journal consistent, LF-only.

Credit: @hbilal9 (upstream Dokploy#4844).