build(bazel): remove workaround no longer needed for module names for ngfactory & ngsummary files (angular#25604)

Workaround was added in angular#25335. It was necessary for .ngfactory & .ngsummary files to have proper AMD module names starting with @angular when building angular downstream from source using Bazel. The underlying issue has been resolved in the compiler and these files now get proper AMD module names without the need for this workaround. The workaround had an unexpected consequence angular/angular-cli#11835 which is fixed by its removal.

PR Close angular#25604

Author: gregmagolan

packages/compiler/src/aot/summary_resolver.ts

@@ -120,16 +120,6 @@ export class AotSummaryResolver implements SummaryResolver<StaticSymbol> {
       summaries.forEach((summary) => this.summaryCache.set(summary.symbol, summary));
       if (moduleName) {
         this.knownFileNameToModuleNames.set(filePath, moduleName);
-        if (filePath.endsWith('.d.ts')) {
-          // Also add entries to map the ngfactory & ngsummary files to their module names.
-          // This is necessary to resolve ngfactory & ngsummary files to their AMD module
-          // names when building angular with Bazel from source downstream.
-          // See https://github.com/bazelbuild/rules_typescript/pull/223 for context.
-          this.knownFileNameToModuleNames.set(
-              filePath.replace(/\.d\.ts$/, '.ngfactory.d.ts'), moduleName + '.ngfactory');
-          this.knownFileNameToModuleNames.set(
-              filePath.replace(/\.d\.ts$/, '.ngsummary.d.ts'), moduleName + '.ngsummary');
-        }
       }
       importAs.forEach((importAs) => { this.importAs.set(importAs.symbol, importAs.importAs); });
     }