Description of problem:
This is a tracker for the upstream issue which was reported against BS v1.32.5. There is a PR that's waiting for review.  

There's impact to RHDH because we recommend this config in our docs for prod/high performance scenarios

The impact of not doing anything is, the cache will grow indefinitely in size and key lookups will fail (as stated by the upstream reporter). 

It seems like the use of redissets did not offer much of performance benefit either:

https://github.com/jaredwray/keyv/tree/main/packages/redis#about-redis-sets-and-its-support-in-v4

Note, adopting the fix will result in breaking changes:

• the userRedisSets config will be dropped
• older keys will no longer be valid

Prerequisites (if any, like setup, operators/versions):

Steps to Reproduce

1. <steps>

Actual results:

Expected results:

Reproducibility (Always/Intermittent/Only Once):

Build Details:

Additional info (Such as Logs, Screenshots, etc):