SpawnCommand does not signal when ignoring set_environment_variables

[ahupp]

Is your feature request related to a problem? Please describe.

I'm running Wezterm in windows with a default domain in WSL. I was trying to use SpawnCommandInTab to launch a process, and found the environment from set_environment_variables wasn't passed through. I think this is because of this line in the docs:

This is not used when working with remote domains.

https://github.com/wez/wezterm/blob/0ac1e948c5b4fb1d1dee532eba36c4669a64774e/docs/config/lua/config/set_environment_variables.md?plain=1#L12

Describe the solution you'd like It would be nice if SpawnCommand logged an error in this case, rather than silently ignoring the env.