Reduce allocations from Redis operations

RedisIndexedSessionRepository and RedisSessionExpirationPolicy create a lot of single-use proxies by relying on BoundHashOperations.

For instance in this case:

https://github.com/spring-projects/spring-session/blob/f6f4c8652e03257420bc35f44492c5dc5d4121a9/spring-session-data-redis/src/main/java/org/springframework/session/data/redis/RedisIndexedSessionRepository.java#L898-L903

https://github.com/spring-projects/spring-session/blob/f6f4c8652e03257420bc35f44492c5dc5d4121a9/spring-session-data-redis/src/main/java/org/springframework/session/data/redis/RedisIndexedSessionRepository.java#L733-L735

This showed up in our production profiler because of hundreds of MB allocated in java.lang.reflect.Method:

If I understand the code correctly, this is done purely for convenience and could simply be replaced by the following code:

String key = getSessionKey(sessionId);
sessionRedisOperations.opsForHash().putAll(key, this.delta);

Or am I overlooking something?

Start with RedisIndexedSessionRepository.java at the referenced lines 733-735 and 898-903, then inspect RedisSessionExpirationPolicy for the same BoundHashOperations usage. Compare the direct Redis operations with the current behavior and verify that the change removes unnecessary allocations without altering session updates or expiration handling.