Precompiled 2024-03-25-cdcf47b

split QueryNode::next so the caller handles IndexRangeRequests (#23784)

allow the caller of QueryNode::next to execute index ranges in batches by returning an IndexRangeRequest that should be executed. The response is passed back in to QueryNode::feed. Then the caller calls QueryNode::next again and loops.

considered alternatives:
1. #23743 inverts control completely, pulling the QueryNode logic into a batched function.
2. execute `next()` in parallel, passing in a channel instead of `&mut Transaction`. unfortunately `next()` can call six different methods on Transaction which would all have to be handled by the channel.

GitOrigin-RevId: 7479a27cb2ad6f54c931d0f9f2c029823e3ec3e6