Store Remote Projects elsewhere than in the main config

[SpidFightFR]

Hey everyone, just a feature request, to store Remote Projects configs elsewhere within zed's config files than the main config.

Indeed, the current behavior works really badly with immutable systems such as nixos.
As soon as you enable any type of immutability within zed's config, meaning, a static config generated once and kept as read-only, Remote Projects become a huge pain to deal with it.

This is my proposition:

• $HOME/.config/zed/settings.json should store all the config, that is subject to remain static.
• Another file should be used to store remote projects (e.g: $HOME/.config/zed/remote-projects.json or something)
• Ideally, the ai integration suffers from a similar issue, since the default model is stored in this variable:

"assistant": {
    "button": true,
    "default_model": {
      "model": "<model>",

If you have an immutable config file, the model cannot be changed while in the software, without editing the config file, which implies to re-generate it entirely, on an immutable system.

Thus such assistant configs would better be stored in yet another config file (e.g: $HOME/.config/zed/assistant-settings.json).

I understand that those changes might make the config folder a bit messier but ultimately, such changes would benefit everyone, including people who use immutable systems.

Best regards - Spid.