Handle membrane-backend session data with PostgreSQL

[k-allagbe]

Currently, the session data in membrane-backend is managed using a "filesystem" storage mechanism. This solution is not scalable, posing risks for data loss and limiting the ability to share session states across multiple instances.

Objective

Migrate the session storage to use a PostgreSQL database to improve scalability, persistence, and data integrity.

Tasks

• [ ] Evaluate current session handling code in membrane-backend.
• [ ] Design a schema for storing session data in PostgreSQL.
• [ ] Implement the schema in PostgreSQL.
• [ ] Update session handling in membrane-backend to use the PostgreSQL database.
• [ ] Test the new implementation to ensure data consistency and reliability.
• [ ] Update documentation to reflect the new changes.

Acceptance Criteria

• Session data should be stored in a PostgreSQL database.
• Session handling should work seamlessly with the new database setup.
• Documentation should be updated to explain the new session handling mechanism.

[rngadam]

good work detailing this plan!