search: update zoekt with removal of RepositoryRankRequest

[keegancsmith]

This endpoint was unused which was why it was removed in Zoekt. The changes from Zoekt included in this dep bump:

• sourcegraph/zoekt@1686b50d50 indexserver: remove unused GetRepoRank
• sourcegraph/zoekt@7078a585a9 shards: populate RepoList.Stats.Repos
• sourcegraph/zoekt@b9e6d9433e zoekt-indexserver: Check stderr for git fetch
• sourcegraph/zoekt@93f7b0c983 matchtree: capture Stats before pruning
• sourcegraph/zoekt@7643f3b313 matchiter: capture metric NgramLookups

Test Plan: CI

[jhchabran]

@keegancsmith there are some issues with the back compat tests, I'll fix them tomorrow morning 👍

[keegancsmith]

@jhchabran any luck? I'm just about to update this PR I would love to deploy soon.

[jhchabran]

@keegancsmith I'm on it, stumbled across new problems when I bumped the target for the back compat tests to 5.1.

I haven't touch your PR and I don't think I'll have to, as it'll simply be about rebasing main once I get it working. I'll keep in touch if it takes me too long 🙏

[jhchabran]

@keegancsmith I think it might take me more time to fix this, though I should have it done before EOD.

What about this: you disable the backcompat tests for now, I'll re-enable them on my side. This way you can keep moving with this PR.

[keegancsmith]

@jhchabran I will do that approach if I'm still blocked tomorrow morning. For now I am context switched onto something else :)

[jhchabran]

@keegancsmith my PR is up, so once it's merged, I should be able to ensure this one is green as well :)

[keegancsmith]

@jhchabran mind stamping? rebased :)

[sourcegraph-bot]

Codenotify: Notifying subscribers in CODENOTIFY files for diff 2ec4a57...1d0d79e.

Notify	File(s)
@camdencheek	internal/search/backend/metered_searcher.go
@jtibshirani	internal/search/backend/metered_searcher.go

[jhchabran]

@keegancsmith I'm running a branch with the same thing, it's broken, need to pin the zoekt dep for the backcompat, incoming fix, gimme a minute :)

[keegancsmith]

no worries, FYI I force pushed just before making that comment with the rebase + one extra tiny change to include something new from zoekt in a trace event.

[jhchabran]

@keegancsmith it passed on my branch, pushed the commit here :)

[github-actions]

The backport to 5.1 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-5.1 5.1
# Navigate to the new working tree
cd .worktrees/backport-5.1
# Create a new branch
git switch --create backport-54394-to-5.1
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 49aff3d61c8479a296ba3379e7cabab97635be07
# Push it to GitHub
git push --set-upstream origin backport-54394-to-5.1
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-5.1

Then, create a pull request where the base branch is 5.1 and the compare/head branch is backport-54394-to-5.1.