Failing tests with spaces in path: " Activation Environment" venv tests (#14207)

* Use toCommandArgument()
* Run venv tests in PR validation
* Add venv to mac stage
* Undo pipeline changes
* Custom GHA workflow to run venv tests
* Move to directory with spaces
* Move defaults outside (apply to entire workflow)
* mark env variables as env
* run tests in working directory
* Delete test workflow

Author: kimadeline

src/test/common/terminals/environmentActivationProviders/terminalActivation.testvirtualenvs.ts

@@ -132,7 +132,7 @@ suite('Activation of Environments in Terminal', () => {
     ): Promise<string> {
         const terminal = vscode.window.createTerminal();
         await sleep(consoleInitWaitMs);
-        terminal.sendText(`python ${pythonFile} ${logFile}`, true);
+        terminal.sendText(`python ${pythonFile.toCommandArgument()} ${logFile.toCommandArgument()}`, true);
         await waitForCondition(() => fs.pathExists(logFile), logFileCreationWaitMs, `${logFile} file not created.`);
 
         return fs.readFile(logFile, 'utf-8');