Add support for .code-workspace files

[IronicUsername]

Goal
Have native Zed support for VSCode .code-workspace files

Context
In VSCode they have this concept of "Workspaces" which basically is the idea to have multiple project open in 1 big window [sauce].

The "default" `.code-workspace` file roughly looks like this (click to open):

{
  "folders": [
    {
      "path": "./.github"
    },
    {
      "path": "./frontend",
      "name": "The frontend",
    }.
    {
      "name": "project_root",
      "path": "."
    }
  ],
  "settings": {
    "editor.tabSize": 2,
    "editor.formatOnSave": true,
    "editor.insertSpaces": true,
    "diffEditor.ignoreTrimWhitespace": false,

    // opinionated: see all whitespace characters in a file
    "editor.renderWhitespace": "all",
    // opinionated: see every line "as it is", no trickery done by IDE
    "editor.wordWrap": "off",

    // https://stackoverflow.com/a/729795
    // https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206
    // TL;DR: last line important cause shows some compilers "actual" end of line
    "files.insertFinalNewline": true,
    "files.trimFinalNewlines": true,
    "files.trimTrailingWhitespace": true,

    "files.exclude": {
      "**/.git": true,
      "**/.svn": true,
      "**/.hg": true,
      "**/CVS": true,
      "**/.DS_Store": true,
      "**/Thumbs.db": true,
      ".github": true,
      "frontend": true,
    },
    "[go]": {
      "editor.defaultFormatter": "golang.go",
      "editor.tabSize": 4,
      "editor.codeActionsOnSave": {
        "source.organizeImports": "explicit"
      }
    },
    "[json]": {
      "editor.defaultFormatter": "vscode.json-language-features"
    },
    "[markdown]": {
      "editor.defaultFormatter": "vscode.markdown-language-features",
      "editor.formatOnSave": false
    },
    "[toml]": {
      "editor.defaultFormatter": "tamasfe.even-better-toml"
    },
    "[dockercompose]": {
      "editor.defaultFormatter": "ms-azuretools.vscode-docker",
      "gitlens.codeLens.symbolScopes": ["!module"],
      "editor.autoIndent": "advanced",
      "editor.quickSuggestions": {
        "other": true,
        "comments": false,
        "strings": true
      }
    },
    "[yaml]": {
      "editor.defaultFormatter": "esbenp.prettier-vscode",
      "editor.autoIndent": "keep"
    }
  },
  "extensions": {
    "recommendations": [
      "golang.go",
      "github.vscode-github-actions",
      "tamasfe.even-better-toml",
    ]
  },
  "launch": {
    "version": "0.2.0",
    "configurations": [
      {
        "name": "Remote Debug",
        "type": "go",
        "request": "attach",
        "mode": "remote",
        "port": 12080,
        "host": "${env:REMOTE_HOST}"
        // "trace": "verbose",  // uncomment to see verbose output
      }
    ]
  }
}

Basically its a vscode-settings.json on steroids. A single file to configure parts of vscode for a given project.

It now would be very neat if Zed could understand these settings and can apply them itself.
Additionally it would also be very cool to have a own Zed-version of this .code-workspace file since it makes working in teams easier.

Imo Projects should have only the necessary files in them + as little as possible.
Committing an entire .zed / .vscode folder that consist only out of opinionated editor settings as json files is ugly, annoying and simply not right because it is not crucial to the application's existence.
Heck, one could even Notepad++ that shit..

In Vscode it is entirely on you if you want to use the .code-workspace file or your "own settings"
If altho i would commit the .vscode folder , the user opening vscode will always be forced to use the settings set in the project which is wrong behavior.

[ssergiienko]

Its tracked here #9459