refactor(ivy): create lazy route keys that are similar to ngtools lazy routes

This will make it easier to retrieve routes for specific entry points in
`listLazyRoutes()` (which is necessary for CLI integration but not yet
implemented).

Author: gkalpak

packages/compiler-cli/src/ngtsc/routing/src/analyzer.ts

@@ -38,9 +38,9 @@ export class NgModuleRouteAnalyzer {
 
   add(sourceFile: ts.SourceFile, moduleName: string, imports: ts.Expression|null,
       exports: ts.Expression|null, providers: ts.Expression|null): void {
-    const key = `${sourceFile.fileName}#${moduleName}`;
+    const key = this.entryPointManager.keyFor(sourceFile.fileName, moduleName);
     if (this.modules.has(key)) {
-      throw new Error(`Double route analyzing ${key}`);
+      throw new Error(`Double route analyzing for '${key}'.`);
     }
     this.modules.set(
         key, {

packages/compiler-cli/src/ngtsc/routing/src/route.ts

@@ -30,6 +30,11 @@ export class RouterEntryPointManager {
 
   constructor(private moduleResolver: ModuleResolver) {}
 
+  keyFor(filePath: string, moduleName: string): string {
+    // Drop the extension to be compatible with how cli calls `listLazyRoutes(entryRoute)`.
+    return `${filePath.replace(/\.tsx?$/i, '')}#${moduleName}`;
+  }
+
   resolveLoadChildrenIdentifier(loadChildrenIdentifier: string, context: ts.SourceFile):
       RouterEntryPoint|null {
     const [relativeFile, moduleName] = loadChildrenIdentifier.split('#');
@@ -44,10 +49,9 @@ export class RouterEntryPointManager {
   }
 
   fromNgModule(sf: ts.SourceFile, moduleName: string): RouterEntryPoint {
-    const absoluteFile = sf.fileName;
-    const key = `${absoluteFile}#${moduleName}`;
+    const key = this.keyFor(sf.fileName, moduleName);
     if (!this.map.has(key)) {
-      this.map.set(key, new RouterEntryPointImpl(absoluteFile, moduleName));
+      this.map.set(key, new RouterEntryPointImpl(sf.fileName, moduleName));
     }
     return this.map.get(key) !;
   }