Fix space escaping bug in existing-terminal

When used while HTTP Toolkit was running in a path containing a space,
the quotes in NODE_OPTIONS weren't escaped in the shell script that
included it. That made the shell script invalid, breaking it entirely.
We now ensure that all env var values have any quotes included correctly
escaped.

Author: pimterry

src/interceptors/terminal/terminal-scripts.ts

@@ -71,7 +71,7 @@ ${END_CONFIG_SECTION}`;
 
 // A source-able shell script. Should work for everything except fish, sadly.
 export const getShellScript = (env: { [name: string]: string }) => `${
-        _.map(env, (value, key) => `    export ${key}="${value}"`).join('\n')
+        _.map(env, (value, key) => `    export ${key}="${value.replace(/"/g, '\\"')}"`).join('\n')
     }
 
     if command -v winpty >/dev/null 2>&1; then