Avoid interpolating Copilot suggestion if cursor excerpt differs

Add tab context menu

Flip screen sharing icon states

Restructure randomized integration test to allow editing and replaying a plan, fix discovered bugs

Previously, we could end up with a situation where the host did not
see an operation but a guest that didn't have that buffer open would. When
such guest would finally open the buffer, they would apply the operation
without however sending it to the host. The guest wouldn't bother resyncing
it because it wasn't part of its open buffers.

co-authored-by: Antonio Scandurra <antonio@zed.dev>

Update `Ayu` Theme Family

Previously, if the client was disconnected while the initial worktree
state was being sent, it would not see the remaining state after reconnecting.
This was due to `scan_id` and `completed_scan_id` both being initialized to
`0`, so the client would ask for updates since `0` and get nothing.

This commit changes the worktree to initialize `scan_id` to `1` and
`completed_scan_id` to `0`, so that we get the full worktree again on reconnect.

Previously, we would only cancel pending calls when the room became
empty.

Previously, dropping a oneshot sender didn't wake the receiver.

In the case of Github release deserialize error, log response text

Co-Authored-By: Joseph Lyons <joseph@zed.dev>

Previously, because UpdateProject messages were sent in a separately-
spawned task, they could be sent after CreateBufferForPeer messages that
were intended to be sent after them.

Co-authored-by: Antonio Scandurra <antonio@zed.dev>

The host will send a `SaveBuffer` message anyway and this prevents re-querying
the database, which could cause two `BufferSaved` messages to race and, as a
result, cause guest to apply them in the wrong order.

Don't panic if worktree was dropped before sending path changes

In `refresh_entry`, we send a message to the `self.path_changes_tx` channel
to notify the background thread that a path has changed. However, given that
`refresh_entry` uses `spawn_weak`, the worktree could get dropped before sending
the message, which could cause a panic.

This commit changes the code to return an error instead of panicking.

Co-authored-by: Antonio Scandurra <antonio@zed.dev>

Co-authored-by: Antonio Scandurra <antonio@zed.dev>