Replace console.log and console.error with NestJS Logger across the codebase

[nanaf6203-bit]

Problem

Multiple instances of console.log() and console.error() exist in: src/auth/rate-limit.service.ts, src/config/swagger.config.ts, src/utils/validate-env.ts, src/notifications/notifications.service.ts, src/users/email-verification.service.ts.

Why It Matters

console.log bypasses NestJS logging infrastructure: logs don't follow configured log levels, no structured metadata, cannot be redirected to external logging services.

Expected Outcome

Zero console.log/console.error calls in production code.

Acceptance Criteria

• All console.log and console.error calls replaced with this.logger
• Appropriate log levels used
• no-console ESLint rule set to error

Files Affected

src/auth/rate-limit.service.ts, src/config/swagger.config.ts, src/utils/validate-env.ts, src/versioning/examples.controller.ts, src/notifications/notifications.service.ts, src/users/email-verification.service.ts

Difficulty

Easy

Estimated Effort

Small (1-2 hours)

Labels

tech-debt, observability

[CyberXpert607]

@CyberXpert607 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I have reviewed the description and I believe I can work on this if assigned
Thanks

ℹ️ Repo Maintainers: To accept this application, review their application or assign @CyberXpert607 to this issue.

[abdoolyaro]

@abdoolyaro has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi, I'd like to take this issue. I can replace all console.log/console.error calls with the NestJS Logger, use appropriate log levels throughout, enable the no-console ESLint rule as an error, and verify the application builds and runs cleanly with the updated logging.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @abdoolyaro to this issue.

[drips-wave]

Congratulations, @abdoolyaro! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @abdoolyaro: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊