Zed no longer inherits environment vars when invoked via terminal

[tylerFowler]

Check for existing issues

• [X] Completed

Describe the feature

At one point invoking the zed CLI command from a shell would cause Zed to inherit the entire environment. This is particularly important for my company's Golang setup, and completely breaks Golang support for my organization as we have special Go environment vars per project repo.

I believe this would be the expected behavior of invoking Zed from a terminal and has precedent from editors like Atom and of course vim.

If applicable, add mockups / screenshots to help present your vision of the feature

No response

[Moshyfawn]

Any chance you have a similar setup to #8633?

[WeetHet]

Any chance you have a similar setup to #8633?

No, this is probably different, that one is about some particular shells and starting zed not from cli