When two cron scheduler instances run against the same jobs.json (e.g.,
a desktop Hermes InProcessCronScheduler and a NSSM-managed
HermesGateway), the cross-process file lock correctly prevents the
loser from firing jobs. However, the "Tick skipped" message was at
DEBUG level, making dual-scheduler suppression invisible in production
logs at the default INFO level.
Change to INFO so operators can see when a scheduler instance is being
suppressed by the lock — this is an expected control-flow outcome, not
diagnostic noise.
Closes#53720