Reconcile duplicate report-export service

[Uyoxy]

Description

Priority
P2

Type / Area
refactor, backend

Suggested Complexity
Medium

Summary
Consolidate the two report-export service implementations.

Problem
src/reports/report-export.service.ts and src/modules/reports/report-export.service.ts both exist, risking divergent export logic.

Scope

In Scope

Identify which is wired into the active reports module
Merge unique logic
Remove the unused copy

Out of Scope

New export formats

Files
src/reports/report-export.service.ts src/modules/reports/report-export.service.ts

Acceptance Criteria

Single canonical service remains
Existing report export tests pass
npm run build succeeds

How to Test
npm run test -- reports
npm run build

PR Requirements

CI checks must pass
npm run test passes
Include screenshots of test results
Link issue using Closes #ISSUE_NUMBER

Project Links
Repository: https://github.com/Stellar-Uzima/Uzima-Backend Community: https://t.me/+qqHJ6Ufbfmk0NzY0

[Chrisbankz0]

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

I would love to work on this issue. I have experience building production ready applications and collaborating through GitHub workflows. I'll carefully analyze the current implementation, propose a reliable solution, and submit a well-tested PR. My focus is on clean code, maintainability, and timely delivery

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

[drips-wave]

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

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

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@Chrisbankz0's PR #835 was approved and merged by @Uyoxy.

🏆 @Chrisbankz0: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (381 total points). Track your full progress on GrantFox.

👏 Great work, @Chrisbankz0! Keep contributing to Stellar-Uzima.

[drips-wave]

This issue has been marked as completed by a Drips Wave moderator for @Chrisbankz0 as part of the Stellar Wave Program's 6th Wave 🥳

Moderator's reason: [Auto-assessed] The contributor successfully consolidated the duplicate services by removing the redundant file and was approved/merged by a maintainer. Although the issue remains open, the PR is correctly linked and the work has been accepted into the codebase.

😎 @Chrisbankz0: 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.

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

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.