Update an existing ERC-721 SeaDrop V1 drop and its stages.

Saves a Creator Studio draft. It does not change the live drop: SeaDrop stages are onchain contract state, so the draft has to be published separately before buyers see it. A 200 here means the draft was accepted, not that the drop changed.

stages replaces the whole set rather than merging, so send every stage the drop should end up with, including ones you are not changing. Reuse an existing stage uuid to update it, supply a new UUID to add one, and omit a stage to delete it.

The stage list has four rules, and rules 2 and 4 interact in a way worth reading before the first attempt:

1. Exactly one stage must be public_sale.
2. That public stage must be first in the array.
3. The presales, meaning every stage after the first, must be contiguous among themselves: each one starts exactly when the previous presale ended. The first presale start time is not constrained.
4. The last presale must end exactly when the public stage starts.

Together, 2 and 4 mean array order is not chronological order: the public stage is listed first and runs last, with the presales running in array order before it. A drop with two allowlist stages therefore sends [public, presale1, presale2] while time runs presale1, then presale2, then public. Rule 3 does not tie presale1 back to the public stage, which is why the chain reads forward from presale1 rather than from the array head.

Per-wallet mint limits are cumulative across stages, so max_total_mintable_by_wallet on a later stage is a running total for the wallet rather than a fresh allowance.