kgo: ignore aborted txns if using READ_UNCOMMITTED

Kafka does not return AbortedTransactions in the fetch response if the
client is using read uncommitted, so kgo works perfectly against Kafka.
Redpanda DOES return AbortedTransactions (today, although this is being
changed) even if the client is using READ_UNCOMMITTED, which causes
records to be skipped. Redpanda is changing, but we can address this in
kgo as well.

Author: twmb

pkg/kgo/source.go

@@ -1192,7 +1192,10 @@ func (o *cursorOffsetNext) processRespPartition(br *broker, rp *kmsg.FetchRespon
 		o.hwm = rp.HighWatermark
 	}
 
-	aborter := buildAborter(rp)
+	var aborter aborter
+	if br.cl.cfg.isolationLevel == 1 {
+		aborter = buildAborter(rp)
+	}
 
 	// A response could contain any of message v0, message v1, or record
 	// batches, and this is solely dictated by the magic byte (not the