🐞 Pass LaunchAgents environment variable to shell

### Description

I have set an environment variable using LaunchAgent (`launchctl setenv XDG_CONFIG_HOME /Users/yochem/Library/Config`) on startup.

It sets `XDG_CONFIG_HOME` to a location so my shell (fish in my case) knows its config location.

When I start iTerm2 or vscode, fish loads its config from the correct location (and XDG_CONFIG_HOME has a value). This is not the case with CodeEdit.

### To Reproduce

1. Create the following file:
~/Library/LaunchAgents/environment.plist

```xml

Label
my.startup
ProgramArguments

sh
-c

launchctl setenv XDG_CONFIG_HOME /tmp

RunAtLoad

```

2. `$ launchctl load ~/Library/LaunchAgents/environment.plist`
3. Open vscode, its terminal and run `$ echo $XDG_CONFIG_HOME`
> should show an empty line
4. Open CodeEdit, its terminal and run `$ echo $XDG_CONFIG_HOME`
> should print `/tmp`

### Expected Behavior

I expect that CodeEdit behaves the same as other applications, and is aware of environment variables set via the LaunchAgent. It should pass this environment to the shell.

### Version Information

CodeEdit: 0.0.3-alpha.36,5650b45
macOS: 14.0
Xcode: Not installed

### Additional Context

_No response_

### Screenshots

VSCode:

CodeEdit:

Commencez par retracer comment CodeEdit lance son terminal intégré et fournit l’environnement du shell ; l’issue fournit environment.plist et une vérification reproductible de XDG_CONFIG_HOME. C’est terminé lorsque le terminal de CodeEdit hérite de la variable LaunchAgent et affiche /tmp en suivant les étapes de reproduction fournies.

Rédigé par le modèle d'indexation à partir du texte de l'issue.