feat(session): add redis session manager

[thoresuenert]

Close #1700

Questions:

• Do we need actions in cleanup function when we set the expiration on the redis stored data?
• Is the RedisSessionConfig the right way to set a prefix for session keys?
• Do we need multiple tagged Redis setups?
• How can we setup the Redis client to a different database for sessions in this scenario? If we want to

Laravel uses multiple configuration an treat redis as database, to separate cache from other things they configure multiple connections to different databases.
The Redis Client itself allows to set the prefix for the client as a whole. From my understanding to support that we need a tagged('session') redis client. I dont understand how to do that without touchung the kv-store.

For example RedisCacheConfig:
The cache uses the same RedisConfig as the RedisSessionConfig and the data will be written in the same database.

[innocenzi]

Is the RedisSessionConfig the right way to set a prefix for session keys?

Yes!

Do we need multiple tagged Redis setups?
How can we setup the Redis client to a different database for sessions in this scenario? If we want to

Good questions, the kv-store doesn't support tagged configs yet but this should be the way to go if we want multiple database support. With a prefix I'd assume it'd be pretty safe to have sessions on the same database as the cache though, but I admit I don't know what are the best practices here

[brendt]

For now I don't think we should widen the scope of this PR, and just assume one Redis instance. We can add tagged Redis configs later, but let's not complicate this PR with it.

Apart from that, all looks fine!

[brendt]

@innocenzi did you still have an open change request?