ci: set CHROME_PATH environment variable to Bazel's Chrome install

This variable is used by Chrome launcher under Web Test Runner to find and execute Chrome.

tests/legacy-cli/e2e.bzl

@@ -103,6 +103,7 @@ def _e2e_tests(name, runner, **kwargs):
     # Chromium browser toolchain
     env.update({
         "CHROME_BIN": "$(CHROMIUM)",
+        "CHROME_PATH": "$(CHROMIUM)",
         "CHROMEDRIVER_BIN": "$(CHROMEDRIVER)",
     })
     toolchains = toolchains + ["@npm//@angular/build-tooling/bazel/browsers/chromium:toolchain_alias"]

tests/legacy-cli/e2e/utils/process.ts

@@ -177,6 +177,7 @@ function extractCIEnv(): NodeJS.ProcessEnv {
         v === 'CI' ||
         v === 'CIRCLECI' ||
         v === 'CHROME_BIN' ||
+        v === 'CHROME_PATH' ||
         v === 'CHROMEDRIVER_BIN',
     )
     .reduce<NodeJS.ProcessEnv>((vars, n) => {

tests/legacy-cli/e2e_runner.ts

@@ -206,6 +206,7 @@ setGlobalVariable('package-manager', argv.yarn ? 'yarn' : 'npm');
 // Resolve from relative paths to absolute paths within the bazel runfiles tree
 // so subprocesses spawned in a different working directory can still find them.
 process.env.CHROME_BIN = path.resolve(process.env.CHROME_BIN!);
+process.env.CHROME_PATH = path.resolve(process.env.CHROME_PATH!);
 process.env.CHROMEDRIVER_BIN = path.resolve(process.env.CHROMEDRIVER_BIN!);
 
 Promise.all([findFreePort(), findFreePort(), findPackageTars()])