Allow to set no TTL on items in certain bins

Currently, the Redis module assigns a TTL to all CACHE_PERMANENT items (default ~1 year), even for bins that are effectively bounded in size and rarely updated, such as config, bootstrap, and discovery.

I suggest we explicitly support setting the TTL to 0 (or a negative value) to skip the EXPIRE call entirely for these bins, in settings.php:

$settings['redis_perm_ttl_config'] = 0;
$settings['redis_perm_ttl_bootstrap'] = 0;
$settings['redis_perm_ttl_discovery'] = 0;

This approach reduces unnecessary TTL operations while keeping the intended permanent nature of bounded cache bins.

We also haven't set these ttl values in our settings.php.
We are getting RedisException in our dblog randomly.
We are using pantheon and they are reporting that the main reason that the error RedisException: read error on connection to 10.73.8.170:11034 in Redis->hGetAll() (line 60 of /code/docroot/modules/contrib/redis/src/Cache/PhpRedis.php) is happening is due to the amount of Object Cache that is still in the memory and is causing it to reach the limit of its memory.
Although we are not still convinced that setting ttl will resolve this error.
Not able to understand the cause of it.
These are the recommended values:
$settings['redis.settings']['perm_ttl'] = 2630000; // 30 days
$settings['redis.settings']['perm_ttl_config'] = 43200;
$settings['redis.settings']['perm_ttl_data'] = 43200;
$settings['redis.settings']['perm_ttl_default'] = 43200;
$settings['redis.settings']['perm_ttl_entity'] = 172800;
Also they are using the maxmemory policy is allkeys-lru evict keys by trying to remove the less recently used (LRU) keys first, in order to make space for the new data added.