refactor: Move mock token metadata to a dedicated JSON file

[AlAfiz]

Description

In a previous issue, we created a metadata endpoint but hardcoded the dummy descriptions directly inside the route logic.
This makes the route file messy and difficult to update.
We need to extract this data into a dedicated JSON file within our data/ folder and read from it dynamically.
This separates our data layer from our business logic, keeping the controllers clean.

Requirements

• Create a new file data/tokenMetadata.json.
• Move the hardcoded XLM, USDC, and AQUA objects into this file.
• Update the /api/v1/tokens/:symbol/metadata route to import and search through this JSON file.
• Ensure the route still correctly returns a 404 if the symbol isn't found in the JSON.

[Danitello123]

@Danitello123 has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Good sir/ma
Please I would love to work on this
I would deliver my job well
Let's get the coding started please

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

[drips-wave]

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

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