I'd like to avoid cluttering the top-level namespace with all the platform-
specific types.

Put backtrace on a new line when reporting panics

Update copy path commands

Merge MutableAppContext into AppContext

There may have been a good reason for the difference at some point, or I was
still learning Rust. But now it's just &mut AppContext vs &AppContext.

Check if the buffer already exists *before* overwriting it.
Ignore redundant registrations on remote projects.

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

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

Add close items to left and right

This ensures that two successive file updates coming from the host are
not applied in reverse order.

Increase git diff gutter width slightly

Previously, if the test panicked before it had a chance to fully
apply an operation, it would end up not being saved in the plan.
With this commit we will mark the operation as applied before we
start processing it, and mark it as not applied if, once we're done,
we've found out that it couldn't be applied. This is consistent with
what we do for client operations.

This fixes a bug where the host would momentarily disconnect and the guest
would close and reopen the project. This would cause the host to not observe
the guest closing the project. When the guest tried to open one of the
buffers opened prior to closing the project, the host would not send them the
buffer state because it would still remember that the buffer was shared.

The `shared_buffers` map is now cleared when the host reconnects and will slowly
get re-filled as guests issue `SynchronizeBuffers` requests.

This way, the executor isn't influenced by operations that aren't applicable.

These should use the test context's rng, so that they behave the same whether
a pre-recorded plan was used, or the plan is being generated.

When rejoining a project, if entries were both created and deleted since
joining the project, the guest will receive those entries ids in as
removed.

Without this, the server doesn't get dropped at the end of the test, and we eventually run
out of file handles due to sqlite connections being retained.

Hesitant possible fix for lock screen crash

This may cause issues in this situations but as I cannot repro this I'm
making the call to try something and see how it plays out

Update EULA

Prioritize displaying right statusbar items overtop left items if needed

Invalidate copilot suggestion on backspaces

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

Restore an observation on initialization

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

Disable Copilot entirely for stable releases

We don't want people to be able to override the release channel in
production.

This lets us remove the logic for detecting whether a user is a staff
member.

Iterate some more on Copilot