fix(monitoring): default cleanup cron

[soumajitgh]

Summary

• default remote monitoring cleanup schedules to 0 0 * * *
• backfill blank or whitespace-only persisted schedules through a migration
• normalize blank schedules during remote server setup and fall back safely in the monitoring service
• stop logging the token-bearing METRICS_CONFIG value

Root cause

Remote server setup preserved the schema's empty cronJob default. The monitoring container passed that value to the cron parser, exited on the resulting error, and then crash-looped under its always restart policy.

Validation

• go test ./... (from apps/monitoring)
• pnpm -C apps/dokploy run typecheck
• pnpm exec biome check packages/server/src/db/schema/server.ts packages/server/src/setup/server-setup.ts
• git diff --check

Closes #4950

Greptile Summary

The PR defaults blank remote-monitoring cleanup schedules to a daily midnight cron while preserving valid configured schedules and removing token-bearing configuration logs.

• Updates the server schema default and backfills blank or whitespace-only persisted schedules.
• Normalizes blank schedules during cloud remote-server setup.
• Adds a monitoring-service fallback and tests for empty and invalid schedules.
• Stops logging the complete METRICS_CONFIG environment value.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

_{Reviews (2): Last reviewed commit: "chore: remove superseded monitoring migr..." | Re-trigger Greptile}

Context used:

• Knowledge Base — Server Setup and Packaging