write ensight case after fields

As noted in EP1918, if something causes the surface field writing to crash, the Ensight case file will contain entries to invalid/corrupt files. It thus makes sense to only commit the updates to the case file after the writing has completed.

changed milestone to %v2212

added enhancement label

assigned to @mark

The changes appear to be reasonably contained, but should also verify that other formats (eg, vtk) are similarly handled.

Too late for v2206 at this point.

mentioned in commit cee6524c

closed