Describe the bug
When using the CFP, when using the SDK's default serializer, deserialization failures that occur when processing incoming records fail silently from the client app's perspective.

To Reproduce
Configure CFP for a Cosmos collection and introduce a document to Cosmos which doesn't match the class type into which the CFP will deserialize.

Expected behavior
There should be some indication that a failure is occurring, or at least a way to register a handler for deserialization failures.

Actual behavior
From the library user's perspective, it'll appear that there are no incoming changes for the collection, since the deserialization failure happens silently. This is incredibly difficult to debug, and requires enabling traces.

Environment summary
SDK Version: 3
OS Version: Windows

Additional context
Since deserialization happens before passing control to the CFP user provided change handler, I think it makes sense to add a user-defined exception handler to the serializer options class.