KryoSerializerSnapshot would fail to deserialize if a type is missing

KryoSerializerSnapshot would fail to read successfully if a previously registered Kryo type is not accessible by the restored job (either removed from the classpath, or failed to load for some other reason)

The source of the bug is an early return at [1] ,which would skip the consumption at [2] 
 
 [1] https://github.com/apache/flink/blob/cf7b86de436c8714414f563e8637ceb36ea7aabe/flink-core/src/main/java/org/apache/flink/api/java/typeutils/runtime/kryo/KryoSerializerSnapshotData.java#L310

[2] https://github.com/apache/flink/blob/cf7b86de436c8714414f563e8637ceb36ea7aabe/flink-core/src/main/java/org/apache/flink/api/java/typeutils/runtime/kryo/KryoSerializerSnapshotData.java#L314