kvclient: remove ReturnOnRangeBoundary request option

This was added in #70763 with the intention of using it for the
ExportRequests sent by backup processors.

In #114268 we went with a different approach and this feature has not seen
subsequent use.

BatchRequest options that may result in partial batch results require
special thinking/handling at multiple points in dist_sender, so it seems
sensible to remove this option if it is unused.

Epic: none
Release note: None

Author: stevendanna

pkg/kv/kvclient/kvcoord/dist_sender.go

@@ -1901,7 +1901,6 @@ func (ds *DistSender) divideAndSendBatchToRanges(
 	}()
 
 	canParallelize := ba.Header.MaxSpanRequestKeys == 0 && ba.Header.TargetBytes == 0 &&
-		!ba.Header.ReturnOnRangeBoundary &&
 		!ba.Header.ReturnElasticCPUResumeSpans
 	if ba.IsSingleCheckConsistencyRequest() {
 		// Don't parallelize full checksum requests as they have to touch the
@@ -2006,7 +2005,7 @@ func (ds *DistSender) divideAndSendBatchToRanges(
 				ba.UpdateTxn(resp.reply.Txn)
 			}
 
-			mightStopEarly := ba.MaxSpanRequestKeys > 0 || ba.TargetBytes > 0 || ba.ReturnOnRangeBoundary || ba.ReturnElasticCPUResumeSpans
+			mightStopEarly := ba.MaxSpanRequestKeys > 0 || ba.TargetBytes > 0 || ba.ReturnElasticCPUResumeSpans
 			// Check whether we've received enough responses to exit query loop.
 			if mightStopEarly {
 				var replyKeys int64
@@ -2040,13 +2039,6 @@ func (ds *DistSender) divideAndSendBatchToRanges(
 						return
 					}
 				}
-				// If we hit a range boundary, return a partial result if requested. We
-				// do this after checking the limits, so that they take precedence.
-				if ba.Header.ReturnOnRangeBoundary && replyKeys > 0 && !lastRange {
-					couldHaveSkippedResponses = true
-					resumeReason = kvpb.RESUME_RANGE_BOUNDARY
-					return
-				}
 			}
 		}