debt: better understand how changing depth interval presets works in the `soilDataPush` mutation

[garobrik]

Notes from the original soilDataPush PR:

• depth interval presets are weird. i think i understand why we manually delete all depth intervals when we change presets, but since this is now happening in simultaneously with other operations it raises some questions:
  • should we do that deletion before or after applying other depth interval related changes? i implemented "before"
  • should we just not implement this server-side and rely on clients to send the appropriate set of depth intervals to delete? it seems like we'd be more likely to end up with the client's intended data this way, but not sure how that interacts with concurrent changes. but now that i'm writing this out, i'm thinking that since we're recommending to early users to not make concurrent changes we should prioritize user intent