Fix .env which broke as part of moving cmds to the project service

[sourishkrout]

Please see #492 for details.

Before vs after:

❯ runme run hello1
SOMETHING1=[]
❯ ./runme run hello1
SOMETHING1=[this]

Fixes #492.

[sourishkrout]

@adambabik, please lemme know if this fix works for you. Please ignore the code coverage, it's low due to integration vs unit test (not in coverage report).

Instead of calling this in the Remote/Local runner's New, we could run it as part of applying the withProject option. Wdyt?

[sourishkrout]

@adambabik sounded like you had a hunch here

[sonarcloud]

Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[sourishkrout]

@adambabik, please do a retro-review. Going through a review with @pastuxso right now so we can ship a fix quickly.

[adambabik]

@sourishkrout I think it's ok. The way the environment variables are handled in internal/runner/client is a bit unclear, but in the end all env go to a session which is passed to the runner via ExecutableConfig and from there the env are eventually taken.

I will send a follow up PR with clean up.