create-a-container: do not use the default in-memory session store

[runleveldev]

Issue: Replace in-memory session store with a production-ready backend

Description:
The application currently uses the default in-memory session store from express-session. According to the [official documentation](https://www.npmjs.com/package/express-session#compatible-session-stores), this store is not suitable for production because it leaks memory and does not support scaling across multiple processes or servers.

Recommendation:
Configure a persistent and scalable session store such as:

• Redis (connect-redis)
• Memcached (connect-memcached)
• Database-backed stores like connect-session-sequelize

Benefits:

• Prevents memory leaks and data loss on restart
• Enables horizontal scaling and shared sessions
• Improves performance, reliability, and security in production environments

[runleveldev]

Closed in #104