SMQ-2626 - Add audit logs service for monitoring state changes in entities

[felixgateru]

What type of PR is this?

This is a feature as the audit logs feature, including a new audit-logs service and database to track changes within the system.

What does this do?

• Adds a new audit-logs service to manage audit logs and sets up a PostgreSQL database for storing audit logs.
• Integrates audit logging with the existing authentication and authorization mechanisms.
• Adds API endpoints for retrieving audit logs by ID or retrieving all audit logs with filtering options.
• Implements an event consumer to process events from the event store and create audit logs.
• Adds a audit-logs service as a new subscriber to the Event Store

Which issue(s) does this PR fix/relate to?

• Related Issue Feature: Audit Log for Monitoring State Changes in Clients, Channels, Groups, and Domains #2626
• Resolves Feature: Audit Log for Monitoring State Changes in Clients, Channels, Groups, and Domains #2626

Have you included tests for your changes?

No

Did you document any new/modified feature?

Yes, incode documentation

Notes

sequenceDiagram
    participant ES as Event Store
    participant AL as AuditLogsService
    participant DB as AuditLogsDB

    ES->>AL: Event received
    activate AL
    AL->>AL: Transform event to AuditLog
    AL->>DB: Save AuditLog
    activate DB
    DB-->>AL: Confirmation
    deactivate DB
    deactivate AL

Loading

[arvindh123]

How do we get the previous state ?

[arvindh123]

Are we going to consume all the events