fix(ivy): produce ts.Diagnostics for NgModule scope errors (#29191)

Previously, when the NgModule scope resolver discovered semantic errors
within a users NgModules, it would throw assertion errors. TODOs in the
codebase indicated these should become ts.Diagnostics eventually.

Besides producing better-looking errors, there is another reason to make
this change asap: these assertions were shadowing actual errors, via an
interesting mechanism:

1) a component would produce a ts.Diagnostic during its analyze() step
2) as a result, it wouldn't register component metadata with the scope
   resolver
3) the NgModule for the component references it in exports, which was
   detected as an invalid export (no metadata registering it as a
   component).
4) the resulting assertion error would crash the compiler, hiding the
   real cause of the problem (an invalid component).

This commit should mitigate this problem by converting scoping errors to
proper ts.Diagnostics. Additionally, we should consider registering some
marker indicating a class is a directive/component/pipe without actually
requiring full metadata to be produced for it, which would allow suppression
of errors like "invalid export" for such invalid types.

PR Close #29191

packages/compiler-cli/src/ngtsc/scope/test/local_spec.ts

@@ -126,7 +126,13 @@ describe('LocalModuleScopeRegistry', () => {
     registry.registerNgModule(ModuleA.node, {exports: [Dir], imports: [], declarations: []});
     registry.registerNgModule(ModuleB.node, {declarations: [Dir], exports: [Dir], imports: []});
 
-    expect(() => registry.getScopeOfModule(ModuleA.node)).toThrow();
+    expect(registry.getScopeOfModule(ModuleA.node)).toBe(null);
+
+    // ModuleA should have associated diagnostics as it exports `Dir` without declaring it.
+    expect(registry.getDiagnosticsOfModule(ModuleA.node)).not.toBeNull();
+
+    // ModuleB should have no diagnostics as it correctly declares `Dir`.
+    expect(registry.getDiagnosticsOfModule(ModuleB.node)).toBeNull();
   });
 });