Retain connection to remote projects when temporarily disconnected

Vim f and t bindings

Don't rely on contacts popover or contacts list for theming
Add metrics id to request body
Clean up some code and comments

Co-Authored-By: Mikayla Maki <mikayla.c.maki@gmail.com>

Co-Authored-By: Nathan Sobo <nathan@zed.dev>

Fix callback leaks when subscriptions are added and dropped in the same effect cycle

Co-Authored-By: Nathan Sobo <nathan@zed.dev>

If the host thinks a guest has a buffer that they don't have, the host won't
send it to them when they attempt to open it the next time. This can happen
if the guest disconnected before they received the host's response to an
initial open buffer request.

Co-Authored-By: Nathan Sobo <nathan@zed.dev>

This fixes a leaked handle error.

Co-authored-by: Kay Simmons <kay@zed.dev>

Co-authored-by: Kay Simmons <kay@zed.dev>

Fix a callback leak that would occur when dropping a subscription
to a callback collection after triggering that callback, but before
processing the effect of *adding* the handler.

Co-authored-by: Kay Simmons <kay@zed.dev>

Prefer first max while fuzzy matching projects fixes unexpected behavior

Any buffers we requested but that haven't been fully sent will cause
outstainding open requests to hang. If we re-request them, any
waiting open requests will resume when the requested buffers finish
being created.

Co-authored-by: Max Brunsfeld <max@zed.dev>
Co-authored-by: Mikayla Maki <mikayla@zed.dev>

Appease clippy

Forgetting to do this meant we were unable to sync changes with reconnecting
guests in some cases.

It's possible that the host was disconnected when attempting to notify
guests of a file save, so we need to transmit this in order to correctly
update the file's mtime.

Next failing seed OPERATIONS=200 SEED=6894

We need to know the most recent scan id we have actually completed. This is to
handle the case where a guest disconnects when we're in the middle of streaming
worktree entries to them. When they reconnect, they need to report a scan_id
from before we started streaming the entries, because we have no record of when
the stream was interrupted.

Next failure:
SEED=5051 ITERATIONS=1 OPERATIONS=200 cargo test --release --package=collab random -- --nocapture

Include Typescript completion item `detail` field in completion label

Correct default settings' name key for RA in init options example

When a host sends a buffer to a guest for the first time, they record that
they have done so in a set tied to that guest's peer id. When the guest
reconnects and syncs buffers, they do so under a different peer id, so we
need to be sure we track which buffers we have sent them to avoid sending
them the same buffer twice, which violates the guest's assumptions.

Add dismiss buffer search button & fix some faulty icon button styling

Co-Authored-By: Nate Butler <nate@zed.dev>

Add other line seperators to regex normalization

Add close clean items command