Add campaign API route tests for auth, validation, and rate limits

[pragmaticAweds]

Context

Campaign creation has service and validation tests, but the API route combines JWT auth, route-level rate limiting, controller validation, Cairo client selection, and response mapping. These integration points are not covered by route/controller tests.

Scope

• Add route/controller tests for POST /api/v1/campaigns
• Cover missing/invalid auth token responses
• Cover validation failures for campaign_ref, target_amount, title, and donation_token
• Cover duplicate campaign refs and wallet/balance errors through mocked service dependencies or repositories
• Cover the rate-limit response shape and headers where practical
• Ensure the success response includes campaign ID, ref, target, token, transaction hash, and created timestamp

Out of Scope

• Live Cairo/StarkNet calls
• Campaign listing or update endpoints
• Changing campaign creation business rules

Acceptance Criteria

• Campaign API behavior is covered at route/controller level
• Expected client errors return stable status codes and error codes
• Rate-limit behavior is tested without slowing the suite
• bun run type-check passes
• bun run test passes
• bun run lint passes

Suggested Files or Packages

• src/components/v1/campaign/
• src/components/v1/routes.api.v1.ts
• src/__tests__/
• src/appMiddlewares/jwtAuth.api.ts

[Silver36-ship-it]

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

I would love to work on this professionally, please assign it to me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Silver36-ship-it to this issue.

[daveades]

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

Please let me work on this issue

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

[drips-wave]

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

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