feat(cron): add configurable max_repeat safeguard for cron job repeats (#59333)

[webtecnica]

Add configurable max_repeat safeguard for cron jobs. Reads cron.max_repeat from config (default 1000). Clamps repeat.times at job creation and logs warning. Closes #59333

[teknium1]

Thanks for adding a guardrail around accidental high cron repeat counts. The core idea addresses behavior still present on current main: create_job() stores the supplied repeat value directly at cron/jobs.py:1203-1205.

Problems

• This does not close #59333: that issue concerns Kanban's BLOCK_RECURRENCE_LIMIT, which remains hard-coded at hermes_cli/kanban_db.py:134.
• The cap only runs on creation. cronjob(action="update") writes a supplied repeat directly at tools/cronjob_tools.py:944-949, and update_job() persists it at cron/jobs.py:1319,1387-1388; this bypasses the safeguard.
• The new except Exception: pass around cap application silently permits an uncapped job if validation/import fails.
• Please add cron.max_repeat to DEFAULT_CONFIG and document it; neither hermes_cli/config.py:2673-2740 nor website/docs/user-guide/features/cron.md:558-575 currently exposes this setting.

Suggested changes

• Re-scope/correct the issue reference, centralize repeat validation in cron.jobs, apply it on create and update, and add integration tests for both paths.

This is an automated hermes-sweeper review.

[teknium1]

Swallowing every failure here silently creates an uncapped job, which defeats the safeguard. Please validate or log/reject failures instead of using except Exception: pass.