Implement Structured Logging and Correlation IDs

[snobbee]

Is your feature request related to a problem? Please describe.

Initializing a repository without proper logging practices is a missed opportunity for observability, which could lead to challenges in debugging and monitoring.

Describe the solution you'd like

Implement a structured logging system that:

• Utilizes JSON format for all logs
• Includes essential fields such as timestamp, severity, and correlation ID
• Supports context injection for better traceability
• Offers different log levels (DEBUG, INFO, WARN, ERROR)
• Allows the addition of custom fields for specific use cases
• Provides utilities for performance logging

Describe alternatives you've considered

• Relying on plain text logs and using grep for searching
• Manual JSON formatting for logs
• Using Application Performance Monitoring (APM) tools without structured logging

Additional context

Implementing these logging practices from the start will help ensure we have a solid foundation for observability, enabling easier debugging and monitoring in the future.