improve robustness of DB modification queries

[Kevin Milner]

Queries to update fault/deformation models should be robust to handle errors. Originally, the fault model update SQL consisted of 2 steps. The first would delete everything, then the second would repopulate it. If anything goes wrong in the middle of this, you are left with an empty fault model. I've updated this for Fault Models to use batch committing with rollback on failure, but I still need to do this for Deformation Models and anywhere else in the code that does something similar.

I created the ticket to document this, and will close when all instances are fixed.

[Kevin Milner]

I didn't find any other queries that would benefit from this enhancement...marking as duplicate because it's basically a duplicate of #251 (which I forgot that I created).