Use existing env variables when updating container app if "skipped"

[nturinski]

Fixes #451

Note that this only applies for updateContainerApp since deployWorkspace leverages getDefaultContextValue which sets context.environmentVariables to [ ] if it doesn't detect an .env file.

I didn't change this behavior because I figured that we will be altering deployWorkspace's behavior; specifically we'll be looking at an envPath setting.