BabelStorage::update() silently skips 200-record chunks when any record has duplicate key

Problem/Motivation

The update() method in BabelStorage processes records in chunks of 200. If any single record in a chunk has a duplicate key (already exists), the entire chunk of 200 records gets silently skipped due to how the exception is handled.

New records should be inserted successfully. Only actual duplicates should be skipped