fix(@angular/build): builder removes @angular/localize when external packages are not inlined

The current bundle logic removes any import starting with `@angular/localize` if i18n inline is active.

The i18n inline transformation is only applied to internal packages.

This causes an issue at run time execution of the packages which are external (pre-bundled) and therefore not inlined.

The current fix aims at removing import starting with `@angular/localize` only if both i18n inline is active and there are no external packages.

Author: claudio-roma

packages/angular/build/src/tools/esbuild/application-code-bundle.ts

@@ -654,7 +654,7 @@ function getEsBuildCommonPolyfillsOptions(
   tryToResolvePolyfillsAsRelative: boolean,
   loadResultCache: LoadResultCache | undefined,
 ): BuildOptions | undefined {
-  const { jit, workspaceRoot, i18nOptions } = options;
+  const { jit, workspaceRoot, i18nOptions, externalPackages } = options;
 
   const buildOptions = getEsBuildCommonOptions(options);
   buildOptions.splitting = false;
@@ -671,8 +671,11 @@ function getEsBuildCommonPolyfillsOptions(
   // Locale data should go first so that project provided polyfill code can augment if needed.
   let needLocaleDataPlugin = false;
   if (i18nOptions.shouldInline) {
-    // Remove localize polyfill as this is not needed for build time i18n.
-    polyfills = polyfills.filter((path) => !path.startsWith('@angular/localize'));
+    const isOptimizedBuild = options.optimizationOptions.scripts;
+    if (!externalPackages) {
+      // Remove localize polyfill when i18n inline transformation have been applied to all the packages.
+      polyfills = polyfills.filter((path) => !path.startsWith('@angular/localize'));
+    }
 
     // Add locale data for all active locales
     // TODO: Inject each individually within the inlining process itself