fix: expose stack modules on pool type

[raashish1601]

Summary

createClientPool() from the redis package already injects the default Redis Stack modules, but the package only re-exported RedisClientPoolType from @redis/client, whose default module set is empty. That meant code annotating a pool as RedisClientPoolType lost the json and ft namespaces.

This adds a redis package-level RedisClientPoolType alias with the same default module set as RedisClientType and createClientPool().

Fixes #3149.

Validation

• npm run build
• npx tsc --noEmit --module NodeNext --moduleResolution NodeNext --target ES2022 --lib ES2023 --strict --skipLibCheck --esModuleInterop .tmp-pool-type-test.ts
• npm run lint

---

Note

Low Risk
Low risk type-only change that adjusts exported typings for RedisClientPoolType to match actual module injection behavior; no runtime logic changes.

Overview
Aligns the redis package’s pool typings with createClientPool() behavior by adding a package-level RedisClientPoolType alias whose default generic module set includes the Redis Stack modules (e.g. json, ft, ts, Bloom).

This prevents type annotations using RedisClientPoolType from losing the Stack module namespaces compared to the existing RedisClientType/createClientPool() defaults.

^{Reviewed by Cursor Bugbot for commit d6a5f0b. Bugbot is set up for automated code reviews on this repo. Configure here.}

[nkaradzhov]

Thanks @raashish1601, looking good!