Changed storage for persisted device messages from Postgres to Redis

[ShvaykaD]

Pull Request description

Summary:

This PR migrates the storage of device persisted messages and session context from PostgreSQL to Redis, optimizing data management while introducing Redis as an additional third-party dependency alongside PostgreSQL.

Details:

• Migration to Redis: The data previously stored in the following PostgreSQL tables has been moved to Redis:
  • device_publish_msg: Stored information about device messages, including client ID, serial number, topic, time, packet ID, payload, and other properties.
  • device_session_ctx: Stored session context for devices, including the last updated time, last serial number, and last packet ID.
• Creation of Lua Scripts: Developed Lua scripts to manage the saving of device persisted messages and device session context in Redis. These scripts ensure that the saving process is atomic, preventing inconsistencies and improving data integrity.
• Automatic Cleanup in Redis: Previously, periodic jobs were scheduled to clean up device persisted messages. With the Redis implementation, this cleanup now happens automatically as part of the Lua scripts, reducing the need for additional scheduled jobs.
• Third-Party Dependency Changes: This PR introduces Redis as a required third-party dependency specifically for storing device persisted messages and session context. PostgreSQL will continue to be used in other areas of the project, but Redis will now be an integral component for this specific functionality.

General checklist

• [x] You have reviewed the guidelines document.
• [x] Labels that classify your pull request have been added.
• [x] The milestone is specified and corresponds to fix version.
• [x] Description references specific issue.
• [x] Description contains human-readable scope of changes.
• [x] Description contains brief notes about what needs to be added to the documentation.
• [x] No merge conflicts, commented blocks of code, code formatting issues.
• [x] Changes are backward compatible or upgrade script is provided.

Back-End feature checklist

• [x] Added corresponding unit and/or integration test(s). Provide written explanation in the PR description if you have failed to add tests.
• [x] If new dependency was added: the dependency tree is checked for conflicts.

[dmytro-landiak]

pls add a meaningful description of the PR and mark all points from the checklist that are finished.

[dmytro-landiak]

@ShvaykaD pls resolve conflicts and update all 1.3.1 places in your PR to 2.0.0