fixup! refactor(@angular/build): clean up duplicate of code in the karma builders

Author: alan-agius4

packages/angular/build/src/builders/karma/application_builder.ts

@@ -338,7 +338,7 @@ async function getProjectSourceRoot(context: BuilderContext): Promise<string> {
 }
 
 function normalizePolyfills(
-  polyfills: string[] | undefined = [],
+  polyfills: string[] = [],
 ): [polyfills: string[], jasmineCleanup: string[]] {
   const jasmineGlobalEntryPoint = localResolve('./polyfills/jasmine_global.js');
   const jasmineGlobalCleanupEntrypoint = localResolve('./polyfills/jasmine_global_cleanup.js');
@@ -711,8 +711,6 @@ function getBaseKarmaOptions(
   options: NormalizedKarmaBuilderOptions,
   context: BuilderContext,
 ): ConfigOptions {
-  const singleRun = !options.watch;
-
   // Determine project name from builder context target
   const projectName = context.target?.project;
   if (!projectName) {
@@ -723,13 +721,14 @@ function getBaseKarmaOptions(
     ? {}
     : getBuiltInKarmaConfig(context.workspaceRoot, projectName);
 
+  const singleRun = !options.watch;
   karmaOptions.singleRun = singleRun;
 
   // Workaround https://github.com/angular/angular-cli/issues/28271, by clearing context by default
   // for single run executions. Not clearing context for multi-run (watched) builds allows the
   // Jasmine Spec Runner to be visible in the browser after test execution.
   karmaOptions.client ??= {};
-  karmaOptions.client.clearContext ??= singleRun ?? false; // `singleRun` defaults to `false` per Karma docs.
+  karmaOptions.client.clearContext ??= singleRun;
 
   // Convert browsers from a string to an array
   if (options.browsers) {