refactor(ivy): use FatalDiagnosticError to throw more descriptive errors while extracting queries information (#31123)

Prior to this commit, the logic to extract query information from class fields used an instance of regular Error class to throw an error. As a result, some useful information (like reference to a specific field) was missing. Replacing Error class with FatalDiagnosticError one makes the error more verbose that should simplify debugging.

PR Close #31123

packages/compiler-cli/test/compliance/r3_compiler_compliance_spec.ts

@@ -1985,44 +1985,6 @@ describe('compiler compliance', () => {
 
         expectEmit(source, ContentQueryComponentDefinition, 'Invalid ContentQuery declaration');
       });
-
-      it('should throw error if content queries share a property with inputs', () => {
-        const files = {
-          app: {
-            ...directive,
-            'content_query.ts': `
-            import {Component, ContentChild, Input, NgModule} from '@angular/core';
-
-            @Component({
-              selector: 'content-query-component',
-              template: \`
-                <div><ng-content></ng-content></div>
-              \`
-            })
-            export class ContentQueryComponent {
-              @Input() @ContentChild('foo', {static: false}) foo: any;
-            }
-
-            @Component({
-              selector: 'my-app',
-              template: \`
-                <content-query-component>
-                  <div #foo></div>
-                </content-query-component>
-              \`
-            })
-            export class MyApp { }
-
-            @NgModule({declarations: [ContentQueryComponent, MyApp]})
-            export class MyModule { }
-            `
-          }
-        };
-
-        expect(() => compile(files, angularFiles))
-            .toThrowError(/Cannot combine @Input decorators with query decorators/);
-      });
-
     });
 
     describe('pipes', () => {