Prevent schedule duplication when using cron v3 with multiple instances

[ren0503]

Problem:
Currently, scheduling jobs with cron v3 will duplicate tasks if there is more than one instance running.

Suggested Solution:
Switch to using Redis sorted sets with timestamps to manage scheduling. This will help ensure scheduled jobs are not duplicated across multiple instances, improving reliability.

Expected Benefit:

• Avoids duplicate job execution when running multiple instances.
• Leverages Redis for distributed coordination.

Note: Implementation would require integration with Redis and migration from the current cron v3 scheduler for distributed environments.