fix(ivy): emit generic type arguments in Pipe metadata (#29403)

Previously, only directives and services with generic type parameters
would emit `any` as generic type when emitting Ivy metadata into .d.ts
files. Pipes can also have generic type parameters but did not emit
`any` for all type parameters, resulting in the omission of those
parameters which causes compilation errors.

This commit adds support for pipes with generic type arguments and emits
`any` as generic type in the Ivy metadata.

Fixes #29400

PR Close #29403

packages/core/src/compiler/compiler_facade_interface.ts

@@ -77,6 +77,7 @@ export interface R3DependencyMetadataFacade {
 export interface R3PipeMetadataFacade {
   name: string;
   type: any;
+  typeArgumentCount: number;
   pipeName: string;
   deps: R3DependencyMetadataFacade[]|null;
   pure: boolean;

packages/core/src/render3/jit/pipe.ts

@@ -23,6 +23,7 @@ export function compilePipe(type: Type<any>, meta: Pipe): void {
         ngPipeDef = getCompilerFacade().compilePipe(
             angularCoreEnv, `ng://${renderStringify(type)}/ngPipeDef.js`, {
               type: type,
+              typeArgumentCount: 0,
               name: type.name,
               deps: reflectDependencies(type),
               pipeName: meta.name,