feat: add support for connecting using a IORedis instance

[manast]

No description provided.

[Copilot]

Pull request overview

This PR adds support for passing an existing IORedis instance (either Redis or Cluster) to the taskforce-connector instead of connection options. This provides users with more flexibility and control over Redis connection configuration, particularly useful for advanced scenarios requiring custom IORedis settings.

Key Changes:

• Introduced a union type Connection that accepts either ConnectionOptions or a RedisConnection (IORedis instance)
• Added logic to detect and handle IORedis instances separately from connection options throughout the connection flow
• Updated all Redis client-handling functions to accept an optional redisClient parameter that takes precedence over connection options

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
lib/socket.ts	Refactored Connection interface to support both options and IORedis instances; added type guard for instance detection; threaded redisClient through function calls
lib/queues-cache.ts	Updated updateQueuesCache to accept and propagate optional redisClient parameter
lib/queue-factory.ts	Modified core Redis client functions (getRedisClient, ping, getRedisInfo, execRedisCommand, createQueue) to support existing client instances
lib/index.ts	Exported new types (ConnectionOptions, RedisConnection) to make them available to library consumers
README.md	Added documentation with examples for using existing IORedis instances with both standalone Redis and Redis Cluster

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[github-actions]

🎉 This PR is included in version 1.37.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀