fix(@schematics/angular): set explicit type for the module --route component

`ng generate module --route` generates a component and references it from the routing module
template by its default file and class name (`./foo`, `Foo`). The component inherited the
workspace `type` option, so in workspaces that set it (e.g. after updating to v20) the component
was generated as `foo.component.ts` and the routing module import failed to resolve.

Pass an empty `type`, as the library and app-shell schematics do.

Fixes #34449

Author: MeAkib

packages/schematics/angular/module/index.ts

@@ -183,6 +183,10 @@ const moduleSchematic: RuleFactory<ModuleOptions> = createProjectSchematic(
       path: options.path,
       project: options.project,
       standalone: false,
+      // The route templates reference the component by its default file and class name, so the
+      // component must not inherit a `type` or `exportDefault` from the workspace.
+      type: '',
+      exportDefault: false,
     };
 
     return chain([