Populate environment from shell

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

Send heartbeats in both directions so the server can detect when clients disconnect

* Make advance_clock more realistic by waking timers in order,
  instead of all at once.
* Don't advance the clock when simulating random delays.

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

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

Halt keystroke dispatch when a global action is dispatched

Ensure `active_item_index` doesn't go off the end when closing items

This fixes a bug introduced in #538, where closing the current tab would hide
all the other tabs, if the current tab was the last one.

Also, this commit manually sets the active item index instead of calling
`Pane::activate_item`: even though this introduces a little bit of duplication,
it prevents us from mistakenly calling `deactivate` on the wrong item. This would
happen because `activate_item` looks at `self.active_item_index` to determine
which item to deactivate before setting the new one. However, that index is
potentially invalid because `::close_items` manipulates the `item_views` vector,
so `activate_item` could end up calling `deactivate` on an item view that was
not active in the first place.

Implement close inactive items

When a network connection is lost without being explicitly closed by the
other end, writes to that connection will error, but reads will just wait
indefinitely.

This allows the tests to exercise our heartbeat logic.

Remove the client-only logic for sending protobuf pings.

Co-Authored-By: Nathan Sobo <nathan@zed.dev>
Co-Authored-By: Antonio Scandurra <me@as-cii.com>

Also, make it return a static future.

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

This way, the `clock` crate doesn't depend on the `rpc` crate.

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

This way, `util` does not depend on `clock`.

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

Render overlay after remote project becomes read-only

Co-Authored-By: Antonio Scandurra <me@as-cii.com>
Co-Authored-By: Max Brunsfeld <maxbrunsfeld@gmail.com>

Co-Authored-By: Antonio Scandurra <me@as-cii.com>
Co-Authored-By: Max Brunsfeld <maxbrunsfeld@gmail.com>

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

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

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

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

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

Update zed fonts to 1.2.0

Open untitled buffers via the `Project`

Use LSP range formatting when document formatting is not available

This allows the registration of such buffers in the project, which is necessary
to correctly support `::save_buffer_as` and opens the door to sharing untitled
buffers with guests in the future.

Note that, for now, this disallows guests to create untitled buffers in the
current window and will create a new window instead. This is because we don't
yet have a global way of allocating a buffer's remote id (nor a way of saving
such buffers in the host's worktree) and we instead rely on the local model ID,
which could clash with the host's buffer IDs.

I think we should revisit this once guests can share their untitled buffers
with the host and other remote peers, as well as once we start keying
operations by entry id.

Grow worktrees monotonically when sharing and move most messages to the background

Avoid infinite loop when a language server fails to start

We don't use them, and they add a lot of noise to the test output
when running all tests in the workspace.

Add basic JSON support

The feature doesn't work yet because the JSON language server
only supports *range* formatting, not document formatting.
We need to adjust our code to inspect the server's capabilities
and send range formatting requests instead when needed.

We're going to hold off on doing this right now, because it
will create merge conflicts with the `preserve-worktrees`
branch (#525)

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

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

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

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

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

This accidentally regressed in 53327e2.