Update CDM (in place) webdav implementation so it gracefully handles network disconnects

[Kjames5269]

Description

Upon a network disconnect the current webdav implementation will stop all processing when an error occurs and throws an error to the console. The problem occurs that the state, at least when the metacards are being created, only updates once the entire operation finishes. This can lead to inconsistent states where multiple metacards exist per webdav entry. This is also a problem with delete and potentially a problem for modifications.

Steps to Reproduce (if issue is bug)

1. Start up a webdav server, (follow the directions here to set it up over Tomcat)
2. set a breakpoint in the code @ DavAlterationObserver#177
3. Set up CDM to point to the webdav server
4. Ingest one or two metacards and then shutdown the tomcat server. (Press play one or two times)
5. wait until the error is thrown
6. Start the tomcat server again
7. Query for the metacard, and note there are two of them.

Expected behavior:

The state gets updated after a process successfully completes.
There is only one metacard after a disconnect and reconnect.

Actual behavior:

The state gets updated at the end of the batch.
There are multiple metacards after a disconnect and reconnect

Reproduces how often:

100%

Version

This is a problem on both the [2.13.x], and [master] branches, along with any branch cut from those.

Additional Information

Any additional information, configuration or data that might be necessary
to reproduce the issue.

[Kjames5269]

apologizes on the commit message, these changes will depend upon #4223

[Kjames5269]

Stopping work on this issue.

[shaundmorris]

Closing this issue since work has stopped on it over a year ago.