test: move chrome driver path login inside the protractor config check

The chrome driver path is only needed when protractor config is available.

(cherry picked from commit 6c9e388)

Author: alan-agius4

tests/legacy-cli/e2e/tests/misc/cli-exit-interop.ts

@@ -18,7 +18,7 @@ export default async function () {
     await setRegistry(false);
     await createProjectFromAsset('13.0-project', true);
 
-    // A missing stylesheet error will trigger the stuck process issue with v12 when building
+    // A missing stylesheet error will trigger the stuck process issue with v13 when building
     await moveFile('src/styles.css', 'src/styles.scss');
     await expectToFail(() => noSilentNg('build'));
 

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

@@ -191,17 +191,18 @@ export async function useCIChrome(projectDir: string = ''): Promise<void> {
   const karmaConf = path.join(projectDir, 'karma.conf.js');
 
   const chromePath = require('puppeteer').executablePath();
-  const protractorPath = require.resolve('protractor');
-  const webdriverUpdatePath = require.resolve('webdriver-manager/selenium/update-config.json', {
-    paths: [protractorPath],
-  });
-  const webdriverUpdate = JSON.parse(await readFile(webdriverUpdatePath)) as {
-    chrome: { last: string };
-  };
-  const chromeDriverPath = webdriverUpdate.chrome.last;
 
   // Use Puppeteer in protractor if a config is found on the project.
   if (fs.existsSync(protractorConf)) {
+    const protractorPath = require.resolve('protractor');
+    const webdriverUpdatePath = require.resolve('webdriver-manager/selenium/update-config.json', {
+      paths: [protractorPath],
+    });
+    const webdriverUpdate = JSON.parse(await readFile(webdriverUpdatePath)) as {
+      chrome: { last: string };
+    };
+    const chromeDriverPath = webdriverUpdate.chrome.last;
+
     await replaceInFile(
       protractorConf,
       `browserName: 'chrome'`,