search pagination: some single-repository result sets timeout

Created by: slimsag

this query times out because the Kubernetes repository is too large to search. There must be a better way to handle this? options include:

1. Waiting a longer period of time (is a timeout without escape hatch what the user really wants in this case?)
2. Just making Zoekt faster in this case (probably not possible in this particular query that is haystack-full-of-needles, but would be possible in needle-in-the-haystack queries)