test: allow environment variables in toolkit test scripts #4323

Problem:
- Teams want to re-use the toolkits test script so that they can launch tests outside of the vscode repo. This requires some teams to provide additional information (like environment variables) to the spawned VSCode instance

Solution:
- Allow teams re-using the toolkits test script to set environment variables

Author: jpinkney-aws

scripts/test/launchTestUtilities.ts

@@ -28,14 +28,15 @@ type SuiteName = 'integration' | 'e2e' | 'unit'
  * If you want to run the tests manually you should use the `Run & Debug` menu in VS Code instead
  * to be able to use to breakpoints.
  */
-export async function runToolkitTests(suite: SuiteName, relativeTestEntryPoint: string) {
+export async function runToolkitTests(suite: SuiteName, relativeTestEntryPoint: string, env?: Record<string, string>) {
     try {
         console.log(`Running ${suite} test suite...`)
 
         const args = await getVSCodeCliArgs({
             vsCodeExecutablePath: await setupVSCodeTestInstance(suite),
             relativeTestEntryPoint,
             suite,
+            env,
         })
         console.log(`runTests() args:\n${JSON.stringify(args, undefined, 2)}`)
         const result = await runTests(args)
@@ -56,6 +57,7 @@ async function getVSCodeCliArgs(params: {
     vsCodeExecutablePath: string
     relativeTestEntryPoint: string
     suite: SuiteName
+    env?: Record<string, string>
 }): Promise<TestOptions> {
     const projectRootDir = process.cwd()
 
@@ -89,6 +91,7 @@ async function getVSCodeCliArgs(params: {
         extensionTestsEnv: {
             ['DEVELOPMENT_PATH']: projectRootDir,
             ['AWS_TOOLKIT_AUTOMATION']: params.suite,
+            ...params.env,
         },
     }
 }