Response Normalisation | Normalise GET /account/:id/trades response to remove raw Horizon fields

[Sulex45]

The trades endpoint added in Issue #85 may pass through raw Horizon fields like base_asset_type, counter_asset_code, base_is_seller, and price_r as a fraction object. Ensure the response is fully normalised — all fields camelCase, price_r converted to a single decimal price string, all amounts seven-decimal strings, and all asset fields following the standard { code, issuer, type } shape.

Acceptance Criteria: No snake_case fields or raw fraction objects in the trades response. All conventions match other normalised endpoints. Tests are updated to verify the normalised shape.

[believetimothy]

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

Hello Maintainer, I can fix this issue.

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

[shakurJJ]

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

I would like to work on this issue

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

[drips-wave]

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

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