Carry IP Ranges Over to Renewed Subscriptions

🔍 Problem Statement
As an admin, I experience IP ranges not being carried over when manually renewing a self-renewal subscription, which requires manual re-entry and introduces human error.

💡 User Story
As an admin, I want IP ranges on an expiring subscription to be automatically applied to the renewed subscription, so that I don't need to re-enter them and risk configuration errors.

🎯 Definition of Done
- Given a subscription with IP ranges, when an admin manually renews it, then the IP ranges are automatically copied to the renewed subscription.
- This change impacts the API (subscription renewal endpoint — carry forward IP range config).
- Limitations: IP ranges are copied as-is; admin can edit them post-renewal; applies to admin-initiated manual renewals only.

---

Story As a collaborator, I want to the IP ranges to be carried over when we renew manually a self renewal subscription in order to avoid human errors and reduce manual work. DoD TBD when discussed with tech Product Notes What would you like to be able to do? (One idea per form): Carry IP ranges over to renewal subscriptions. How would that help you?: Less manual entry + human error when renewing accounts on the backend. At present, for accounts without autorenewal, the IPs fall off the subscription and need to be manually added back when a new subscription is created for the same customer. How important is this to you?: Important Email address: hsarner@mit.edu Development Notes Components which the feature touches Details on backend/frontend/API/webhooks/SDK implementation Error handling Logging events Technical doc links which have been updated Breaking changes Usability risks/limitations Impact analysis: (Sample)Added a new JSON key to the object stored in DB, therefor, either a guard in code needs to be added or old lists using Expiry object needs to be adjusted and adding the new JSON key to them. QA steps needed to validate: Check functionality of lists created prior this deployment QA Notes Planned Test cases: Initial Test run: Additional Test run(s): Open Questions Question