chore(deps): upgrade cronstrue to 3.38.0 - #9891

Summary

• Upgrades cronstrue 3.3.0 → 3.38.0 (apps/sim only; no transitive deps, lockfile changes only this package).
• cronstrue is used in one place: parseCronToHumanReadable, which renders the schedule description in the Schedule block's schedule info.
• 3.14 added a trimHoursLeadingZero option, so the regex that stripped the hour's leading zero from cronstrue's output (09:00 AM → 9:00 AM) is replaced by the option. Output is identical: checked against every hour × several minutes plus ranges, lists, and nth-weekday expressions (105 expressions, 0 differences).
• English wording changes visible in Sim (from the release notes and confirmed by running both versions):
  • singular units: 1 * * * * "At 1 minutes past the hour" → "At 1 minute past the hour"
  • minute 0 with an hour step: 0 */2 * * * "At 0 minutes past the hour, every 2 hours" → "On the hour, every 2 hours"
  • day-of-month steps: 0 0 */2 * * "every 2 days" → "every 2 days in a month"
  • Every other expression the schedule builder generates (minutes, daily, weekly, monthly) renders exactly as before.
• Stricter validation (zero steps, out-of-range range ends, #0/#6 nth weekdays) now throws in cronstrue. Every newly throwing expression is already rejected by croner, so validateCronExpression refuses it before a schedule is saved; if one is already stored, the existing fallback shows Schedule: <expr> instead of misleading text like "on the null Monday" or "January through undefined". No change to Sim's validation needed.
• No UI copy or docs hard-code cronstrue's wording.

Type of Change

• Other: dependency upgrade

Testing

• Ran the same expressions through 3.3.0 and 3.38.0 with Sim's exact options, with croner checking validity for each: every builder path (minutes intervals 1-1440, hourly minutes 0-59, daily times, weekdays 0-6, month days 1-31), the test fixtures, and ~35 common custom crons (ranges, lists, L, W, #n, #L, macros, 6-field). The only differences are the wording changes above and the newly throwing expressions, all of which croner already rejects.
• Called the real parseCronToHumanReadable from the branch with and without a timezone. The new wording, the #L normalization, the timezone suffix, and the Schedule: <expr> fallback all work.
• utils.test.ts: the description tests now use exact strings (they were mostly toContain) and cover the singular-unit and step wording. Without trimHoursLeadingZero the builder test fails (At 09:00 AM). lib/workflows/schedules/ tests: 58 passed.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

🤖 Generated with Claude Code