Build-a-Box — fix for option save errors when reusing a freed size

A bug in Build-a-Box plan option management has been fixed. When a merchant removed one size option and reused that size name for a different option in the same edit session, saving the plan returned an error and the changes did not persist.

The root cause was the order in which option changes were applied on the backend: creates ran before deletes, so reusing a freed size triggered a uniqueness collision before the old record was removed. The fix reorders the operations — deletes first, then updates, then creates — and wraps the step in a database transaction so partial changes no longer leak on failure.

If you edit your Build-a-Box plan options and include a size that was previously used and removed in the same session, the save now succeeds.