Memory leak: Redis clients are not closed

My understanding after reading the code of this library is that the Redis clients that are created by the default configuration are never closed.

To mitigate the memory leak, one can use the library like this to take control over the client lifecycle:

const redisUrl = '...'

const publisherRedisClient = createClient({ url: redisUrl })
await publisherRedisClient.connect()

const subscriberRedisClient = createClient({ url: redisUrl })
await subscriberRedisClient.connect()

const resumableStreamContextOpts = {
  waitUntil: null,
  publisher: publisherRedisClient,
  subscriber: subscriberRedisClient,
}

No files or tests are named. Start by tracing how the default configuration creates its Redis publisher and subscriber clients, then compare that with the caller-managed lifecycle shown in the issue. Done means the default-created clients have a defined cleanup path and the memory leak scenario is covered by a regression test.