feat(factory, stream, oracle): doc comment, oracle reconfig safety, combined top-up, batch cancel (#212, #206, #205, #204)

[Odkinggjnr]

Summary

• Enhancement: DripFactory::streams_by_recipient has no doc comment #212 — streams_by_recipient doc comment: Added rustdoc to DripFactory::streams_by_recipient mirroring the existing doc comment on streams_by_sender, documenting pagination behavior and the empty-vector-on-overflow contract.

• Enhancement: configure_oracle allows silent reconfiguration with no validation against existing price data #206 — configure_oracle silent reconfiguration safety: configure_oracle now detects when decimals or asset_peg changes relative to the stored config and clears all existing price data (DataKey::Price, per-feeder DataKey::Submission entries, and the DataKey::Submitters list). This prevents stale prices submitted under the old config from being silently misinterpreted under new parameters — get_twap_price returns NoPriceAvailable until a fresh submit_price is made. Changes to max_staleness or oracle_address alone do not clear price data, as those do not affect price magnitude interpretation.

• Enhancement: top_up and extend_duration have no combined convenience call #205 — top_up_and_extend combined convenience call: Added DripStream::top_up_and_extend(env, caller, amount, extra_time_seconds) that deposits funds and extends end_time in a single authorized call, reducing round-trips and the risk of a sender performing only one half of the pair. Follows the same state::with_guard re-entrancy pattern, auth via require_sender_or_operator, and event emission as the existing top_up and extend_duration.

• Enhancement: create_batch_streams has no equivalent batch-cancel counterpart #204 — cancel_batch_streams batch cancellation: Added DripFactory::cancel_batch_streams(env, sender, stream_addresses) that cancels multiple streams in one transaction via cross-contract calls to DripStream::cancel, matching the bulk-creation ergonomics of create_batch_streams. Bounded by the same MAX_BATCH_SIZE (100), with EmptyBatch / BatchTooLarge guards. Atomicity is inherited from Soroban's all-or-nothing transaction semantics. Added drip-stream as a dependency of the factory crate for the cross-contract client.

Test plan

• Oracle reconfig tests: Verify price data is cleared when decimals changes, when asset_peg changes, and that price is preserved when only max_staleness changes (no false positive clearing).
• top_up_and_extend tests: Happy-path (balance + end_time update), zero-amount rejection (InvalidAmount), zero-time rejection (InvalidTimeRange), cancelled-stream rejection, and open-ended stream rejection.
• cancel_batch_streams tests: Empty batch rejection (EmptyBatch), oversized batch rejection (BatchTooLarge).
• Existing tests: All existing unit and integration tests continue to pass.

Closes #212
Closes #206
Closes #205
Closes #204

[drips-wave]

@Odkinggjnr Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[Jaydbrown]

Reviewed and all four sub-fixes (#212, #206, #205, #204) check out correctly — good auth gating, overflow checks, and test coverage throughout. This now has a real merge conflict against main (likely from #265's shared drip-common TTL-constants crate landing first, which this PR also touches). Could you rebase onto current main? Will merge right after.