This reverts commit ae8dd1e3fd0f2ab6d38a1387479cb7806264a7e7, reversing
changes made to 96d5dcadf1981c135be3788b92d18b598c9a2cb0.

Fix goto links with selections

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

This fixes an annoying issue where if the last mouse moved event was
during a drag it would never trigger mouse cursor changes until next
mouse move reset it. It makes sense to continue to not change the cursor
while the button is pressed so instead this tracks when the mouse button
is released in order to update the mouse move event

Co-Authored-By: Antonio Scandurra <me@as-cii.com>

IME Changes: Tracking PR

Fix crash when closing a window while in full-screen mode

This commit delays closing the native window to the next tick to
avoid borrowing either `WindowState` or `MutableAppContext` twice.

Fix focus regression in contact finder

Co-Authored-By: Antonio Scandurra <me@as-cii.com>

Create buffers for remote collaborators out of band

Previously, we would use `Project::serialize_buffer_for_peer` and
`Project::deserialize_buffer` respectively in the host and in the
guest to create a new buffer or just send its ID if the host thought
the buffer had already been sent.

These methods would be called as part of other methods, such as
`Project::open_buffer_by_id` or `Project::open_buffer_for_symbol`.
However, if any of the tasks driving the futures that eventually
called `Project::deserialize_buffer` were dropped after the host
responded with the buffer state but (crucially) before the guest
deserialized it and registered it, there could be a situation where
the host thought the guest had the buffer (thus sending them just the
buffer id) and the guest would wait indefinitely.

Given how crucial this interaction is, this commit switches to creating
remote buffers for peers out of band. The host will push buffers to guests,
who will always refer to buffers via IDs and wait for the host to send them,
as opposed to including the buffer's payload as part of some other operation.

Fix divergence bug in undo/redo

As part of #1405, we changed the way we performed undo and redo to
support combining transactions that were not temporally adjacent for
IME purposes.

We introduced a bug with that release that caused divergence
when performing undo: the bug was caused by only changing the visibility
of fragments whose insertion id was contained in the undo operation. However,
an undo operation also affects deletions which we were mistakenly not
considering. Randomized tests caught this but I guess we didn't run enough
of them.

Fix crash when attempting to show file prompt while using Japanese keyboard layout

Fix panic on main

Remove unused http-auth-basic dependency

Terminal cursor blinking

Clear any stale go-to-definition link when resizing the buffer font