Currently, the cleanupESCAnchors function, which is used by cleanupStructuredEncryptionData command, only logs a warning when it runs into write errors while performing the anchor deletes. This is an issue because if the anchors are not being deleted due to these ignored errors, and the cleanup command then drops the "esc.deletes" collection, then these anchors will never be removed from the ESC because subsequent cleanup calls will only record anchor IDs starting from the new "bottom" position in the null anchor.

Therefore, if a write error occurs during the anchor removal, it should stop the entire cleanup operation so that the "esc.deletes" collection won't be dropped.  Subsequent calls to cleanup can then resume deletions from the leftover "esc.deletes" collection.