Consolidate CreateStreamInput and CreateStreamParams structs in the contract

[Austinaminu2]

Description

`CreateStreamInput` and `CreateStreamParams` (`contracts/streaming/src/lib.rs:152-176`) are field-for-field identical structs.

Task

Either merge them into a single type used by both the single-stream and batch-create paths, or — if there's a reason to keep them separate (e.g. future divergence) — add a doc comment on each explaining why the duplication is intentional.

Good for contributors because

Clear, well-scoped simplification with an easy correctness check (compile + existing tests still pass).

[Ire12]

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

Hey maintainer, please assign the issue to me

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

[adewaleomolara522-coder]

@adewaleomolara522-coder has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi Maintainer, I understand the problem and am confident I can provide a high quality fix, kindly assign this issue to me thanks

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

[nasirudeenbadirudeen87-cloud]

@nasirudeenbadirudeen87-cloud has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I'd be glad to handle this issue. I'll keep the implementation concise, maintainable, and well-documented

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

[soma-enyi]

@soma-enyi has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi team, I'd like to work on this issue. I'm a full-stack developer experienced in TypeScript, Rust, and smart contract development across EVM and Soroban/Stellar ecosystems. I've built and shipped production systems covering backend APIs, frontend interfaces (Next.js, React), CI/CD pipelines, and onchain protocols — so I'm comfortable working across whatever layer this issue touches. My approach I'll start by reproducing the issue locally and reading the surrounding code to understand context and constraints. I'll scope the fix tightly to avoid unnecessary churn, write or update tests to cover the change, and make sure linting, formatting, and existing CI checks all pass before opening a PR. If anything in the issue is ambiguous, I'll flag it early rather than guess. What you can expect A single clean PR with a clear description linking back to this issue. Minimal, well-tested changes that follow the project's existing conventions. Fast turnaround — I'm available to start immediately and responsive to review feedback. Happy to discuss the approach further if needed. Looking forward to contributing.

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

[drips-wave]

Congratulations, @soma-enyi! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

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