feat(BUX-605): gin logs & debugPrint handled by zerolog

[chris-4chain]

Pull Request Checklist

• 📖 I created my PR using provided : CODE_STANDARDS
• 📖 I have read the short Code of Conduct: CODE_OF_CONDUCT
• 🏠 I tested my changes locally.
• ✅ I have provided tests for my changes.
• 📝 I have used conventional commits.
• 📗 I have updated any related documentation.
• 💾 PR was issued based on the Github or Jira issue.

This PR addresses several aspects of logging within a Gin application:

• Internal debugPrint function: Gin's internal debugPrint function implemented in gin as: (fmt.Fprintf(DefaultWriter, "[GIN-debug] " + format, values...)) has been configured to use our zerolog logger by setting the DefaultWriter early in the initialization process.
• Error Logging: The DefaultErrorWriter has also been set to use our zerolog logger. This ensures that errors, such as those caught by gin.Recovery(), are logged consistently.
• Request Logging Middleware: I've created custom Gin middleware to log incoming requests in a structured format using zerolog. This ensures that request data (path, status code, etc.) is captured in well-defined fields for easier analysis.

How it works:

1. When debug mode is enabled, Gin's startup messages are logged through our zerolog setup (customized DefaultWriter).
2. Our custom middleware intercepts each request and generates a structured zerolog record.
3. Gin's standard Recovery middleware now logs errors and panics to zerolog (customized DefaultErrorWriter).

Release Mode:

I've added a new configuration option release_mode (true/false) to control Gin's debug mode. Setting this to true is essential for production environments.

Example log record:

Info about DefaultWriter:
gin-gonic/gin#1877 (comment)

[github-actions]

Manual Tests

💚 Manual testing by @pawellewandowski98 resulted in success.