Standardize backend logging and remove direct console usage

[pragmaticAweds]

Context

Several backend paths still use console.error, console.warn, or console.info directly, including distribution services/controllers, database reset handling, migration generation, and utility transaction handling. The project already has a logger utility, so production logs should use one consistent path and avoid ad hoc console output.

Scope

• Replace direct console usage in backend runtime code with src/utils/logger
• Keep test-only console usage unchanged unless it affects output quality
• Ensure logged errors include useful context without leaking secrets or request tokens
• Align distribution and donation controller logging with shared error handling conventions
• Add lint rule or documented convention to prevent new direct console usage where practical

Out of Scope

• Introducing a new logging provider
• Changing log transport infrastructure
• Rewriting the global error handler

Acceptance Criteria

• Runtime backend code no longer uses direct console.* for errors/info/warnings
• Logger usage includes actionable context for failures
• No secrets or authorization headers are logged
• bun run type-check passes
• bun run test passes
• bun run lint passes

Suggested Files or Packages

• src/components/v1/distribution/
• src/components/v1/Donation/
• src/config/persistence/data-source.ts
• src/scripts/generate-migration.ts
• src/utils/
• eslint.config.mjs

[Ebenezer199914]

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

i will love to work on this issue

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

[Tobi-8]

@Tobi-8 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

please maintainer , assign me to this issue. I have looked through your description, and i have had experience in this type of issue.
kindly assign

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

[mrmoney10010-design]

@mrmoney10010-design has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi! I'd like to work on this issue.

I'll replace direct console.* usage in backend runtime code with the shared logger, ensure logs include useful context without exposing sensitive data, align logging with existing error-handling conventions, and add a lint rule or documented guideline to discourage new console.* usage. I'll verify the changes with type-check, lint, and test runs.

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

[drips-wave]

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

🧑‍💻 @Ebenezer199914: 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 🌊