Unsafe API keys on settings.json, unable to use env variables

[ferrao]

It's a common practice to have dot/config files under revision control to facilitate the usage and management of such configurations across multiple machines.

But recently, I am unable to do this with Zed's settings.json as most MCP server extensions read their API Keys directly from it and there does not seem to be a way to refer to an environment variable in there.