[FE-26] Build DocumentExportButton

[mftee]

Problem

The PDF and Excel export endpoints (BE-16, BE-17) are implemented but unreachable from the UI. Users cannot export their document records for compliance or legal purposes.

Proposed Solution

Create a DocumentExportButton component inside frontend/module/components/export-button/ that provides a dropdown to trigger PDF or Excel exports.

Acceptance Criteria

• Renders a button labeled Export with a chevron icon that opens a dropdown menu on click
• Dropdown contains two options: Export as PDF and Export as Excel
• Export as PDF calls GET /api/module/documents/:id/export/pdf and triggers a browser file download
• Export as Excel (on the document list page) calls GET /api/module/documents/export/excel and triggers a browser file download
• Shows a loading spinner on the selected option while the download is being prepared
• Shows a toast error message if the export request fails
• Accepts a documentId prop for single-document PDF export; when not provided renders only the Excel option
• All component files live inside frontend/module/components/export-button/

[Auwal007]

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

Let me work on this issue please.

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

[Thommyy7]

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

Hi, I’d like to work on this issue.

I’m a software engineer with experience in Rust and systems programming, with a strong focus on writing reliable, efficient, and maintainable code. I’m comfortable working with Rust tooling, testing frameworks, and contributing to open-source projects.

I’ve reviewed the issue and I’m confident I can implement a solid solution while following the project’s conventions and best practices.

Please assign this issue to me — I’d be happy to contribute.

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

[drips-wave]

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

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