PartitionRecords.fetchRecords(...) should defer exception to the next call if iterator has already moved across any valid record

Suppose there are two valid records followed by one invalid records in the FetchResponse.PartitionData(). As of current implementation, PartitionRecords.fetchRecords(...) will throw exception without returning the two valid records. The next call to PartitionRecords.fetchRecords(...) will not return that two valid records either because the iterator has already moved across them.

We can fix this problem by deferring exception to the next call of PartitionRecords.fetchRecords(...) if iterator has already moved across any valid record.