Extenion behaves *terribly* with an unreachable server

### Steps To Reproduce

1. Bitwarden's server is unreachable sporadically (edit: to clarify **my** Bitwarden client's configured server is unreachable sometimes [due to Tailscale accounts, etc]. Not the hosted main Bitwarden server).
2. Try to do anything create/edit-wise

Given the scenario is a "client disco'd from server", I feel safe in saying that using a third-party server is not the culprit here. Thanks for your consideration/time.

### Expected Result

Any of these are better that current behavior:
* It warns you that it's disconnected
* It blocks you from edits
* It stages edits/creates and tries to sync them when online (even if just bails immediately if remote changed, it would still be better for 99% of use-cases)

### Actual Result

* It... acts like it's saving and then fails or hangs, etc.

### Screenshots or Videos

_No response_

### Additional Context

_No response_

### Operating System

Linux

### Operating System Version

nixos (nixos-unstable)

### Web Browser

Firefox

### Browser Version

latest

### Environment Versions

Version: 2025.10.0

SDK: 'main (d0262d3)'

Server version (Third-party): 2025.6.0

Connected to third-party server implementation, Vaultwarden. Please verify bugs using the official server, or report them to the third-party server.

### Issue Tracking Info

- [x] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

Start by reproducing create and edit actions in the browser extension while the configured server is unreachable, then trace the save and sync entry points. Compare the resulting failure or hang with the issue's expected disconnected behavior and define one consistent outcome before implementation; done means edits no longer appear to save silently or hang offline.

Written by the indexing model from the issue text.