Don't rely on `Buffer::edits_since` to keep `FoldMap` up-to-date

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

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

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

Use `&'a Snapshot` directly instead of `impl Into<Content<'a>>`

The text::Buffer and its snapshot already used the same representation
for their content, so we can just make Buffer deref to a Snapshot.

Improve file navigation by naming the root of every crate after the crate itself

Co-Authored-By: Max Brunsfeld <maxbrunsfeld@gmail.com>

Co-Authored-By: Max Brunsfeld <maxbrunsfeld@gmail.com>

Co-Authored-By: Max Brunsfeld <maxbrunsfeld@gmail.com>

Avoid building up pending edits when soft wrapping is disabled

This was causing us to get slower over time as we stacked up hundreds of thousands of pending edits whenever soft wrap was disabled.

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

Use display coordinates for the highlighted row in "go to line"

Fix flaky contacts test

We perform an async fetch of client_b's user data on worktree_a, which ends up holding a handle that prevents worktree_a from being released later in the test. By waiting for this fetch to finish before proceeding, we can be sure worktree_a actually gets released.

A more comprehensive fix would be some way to ensure we actually perform a release if an entity is fully dropped outside of an update cycle, but this fixes the issue for now.

Co-Authored-By: Max Brunsfeld <max@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>

Paint highlighted lines correctly when horizontally scrolled

Override soft-wrap settings for Markdown and Plain Text

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

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

Show collaborators for the active worktree in the titlebar

This makes it easier to integration test peer interactions because now we know their PeerIds.

This will make it possible for us to render their avatars. Previously we only had the user ids. During rendering, everything needs to be available synchronously. So now, whenever collaborators are added, we perform the async I/O to fetch their user data prior to adding them to the worktree.

This will allow them to fetch user data when peers are added or removed. Still work to do though.

We can use this to render avatars.

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

Yeah, it's true they're people, but this is a more specific way in which they're people.

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

Again, this is about reserving the concept of a "collaborator" for actual collaborators on a worktree.

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

This will allow us to use the word "collaborator" to describe users that are actively collaborating on a worktree.

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

This will help us render the collaborator avatars for the active worktree when we know its peers.

This is similar to the active entry, but it can remain assigned even if there is no active entry and we can potentially manipulate it in other scenarios such as interaction with the project browser. This prepares the ground to show the collaborators for the active worktree.

Preserve selection when clicking on editor dismisses go-to-line dialog

Implement select next (cmd-d) and replace selection with next (cmd-k cmd-d)