SDK: standardize transaction response objects

[Otaiki1]

Build location

Work primarily in sdk/src/contract/response.ts. Keep related tests/docs beside that package unless this issue explicitly calls for a cross-package update.

Why this matters

SDK methods should return consistent response objects across create, buy, refund, cancel, and admin operations.

What to build

• Define shared TxResponse and domain-specific extensions.
• Include txHash, ledger, status, feeCharged, resultXdr if safe, and warnings.
• Update module services to use the shared type.

Acceptance criteria

• Tests assert response shape for raffle, ticket, and admin operations.
• Public TypeDoc shows the shared response contract.

Suggested verification

cd sdk && npm run lint && npm run test && npm run build

[ShantelPeters]

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

i would like to work on this issue , kindly assign please

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

[drips-wave]

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

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