refactor: consolidate logger usage

[nanaf6203-bit]

Summary

Logger usage is inconsistent: some files import logger from @/utils/logger, others from @/utils/structuredLogger; some call console.error directly.

Affected area

Whole repo. Notable offenders: src/components/ViewToggle.tsx, src/components/TransactionDetailsModal.tsx, src/utils/earlyErrorSuppression.ts.

Expected behaviour

Choose one canonical logger; deprecate the other in favour of a thin wrapper. Provide a single import path.

Acceptance criteria

• Single canonical logger documented in README.
• Codemod or ESLint rule applied to migrate remaining files.
• No references to the deprecated module remain outside the wrapper.

---

Filed automatically as part of the PropChain code-review sweep.

[Killerjunior]

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

Hi, I would love to work on this issue. Kindly assign.

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

[Jonathan-ai9]

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

Hello,I'd like to work on this issue. I'll standardize logging across the repository by selecting a single canonical logger, introducing a compatibility wrapper for the deprecated implementation, migrating existing imports to one common entry point, replacing direct console.* usage where appropriate, and documenting the logging convention in the README. I'll also add an ESLint rule or codemod to prevent regressions and ensure no direct references to the deprecated logger remain outside the wrapper.

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

[Mirabel64]

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

Hello maintainer, can I work on this please

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

[drips-wave]

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

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

[drips-wave]

This issue has been completed by @Mirabel64 as part of the Stellar Wave Program's 6th Wave 🥳

😎 @Mirabel64: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.