When using the BatchedCollectionCatalogWriter in combination with WriteUnitOfWork the cloned writable collection instance should roll back and be discarded like it behaves for regular writes when the WUOW rolls back.

Currently, stale state can leak into the writable collection instance when the WriteUnitOfWork rolls back, making it more difficult to rely on the copy-on-write semantics over having to manually implement onRollback handlers.