This adds detailed logging to help identify where deadlocks occur in the Redis client.
Each promise gets a unique ID to track its full lifecycle from creation to completion.

Logging added:
- Promise lifecycle: creation, queueing, completion/failure with unique IDs
- Queue state tracking: requests and responses queue sizes throughout operations
- Send operations: request processing, connection writes, promise movement to response queue
- Receive operations: response processing, promise completion
- Error handling: detailed error scenarios and promise cleanup
- Runner fiber: send/receive fiber lifecycle and failure/retry scenarios

Log prefixes:
- [REDIS-INIT]: Executor initialization
- [REDIS-EXEC-{id}]: Individual request/promise lifecycle
- [REDIS-SEND]: Send fiber operations
- [REDIS-RECV]: Receive fiber operations
- [REDIS-ERROR]: Error handling scenarios
- [REDIS-RUNNER]: Runner fiber lifecycle

This will help identify deadlock scenarios in CI environments by showing:
1. If promises are getting stuck at promise.await (no completion logs)
2. If requests are getting stuck in queues (queue size logs)
3. If send/receive fibers are failing (runner logs)
4. If error handling is working properly (error logs)