Introduce Redis Support for Distributed Lock Management

[apoca]

This Pull Request introduces the ability to use Redis for distributed lock management in the scheduler, enhancing its capability to prevent job overlap in distributed environments. While the existing file-based lock mechanism works well for single-instance deployments, modern cloud-based and containerized applications often require a more scalable solution. Redis, being a fast, in-memory data store, offers a robust and efficient way to manage locks across multiple instances.

Implementation Details

• Redis Integration: The PR adds optional support for Redis as a method for managing job locks. Users can now pass a Redis client instance to the Scheduler, enabling Redis-based lock management with minimal configuration.
• Backward Compatibility: This feature is designed to be fully backward compatible. Users can choose between the existing file lock mechanism and Redis based on their deployment needs. The default behavior remains unchanged, ensuring that existing applications will not be affected.
• Flexibility: In addition to supporting distributed environments, this feature provides flexibility for custom lock management strategies. Users can specify custom Redis key prefixes and leverage Redis' capabilities for advanced lock management scenarios.

Usage Example:

$redis = new Redis();
$redis->connect('127.0.0.1', 6379);
// Optional: $redis->auth('yourpassword');

$scheduler = new Scheduler([
    'redisClient' => $redis,
    'redisPrefix' => 'my_app_prefix:'
]);

$scheduler->php('script.php')->onlyOne();