fix(ivy): reflect animations field directly into the output definition (#26322)

The 'animations' field of @Component metadata should be copied directly
into the ngComponentDef for that component and should not pass through
static resolution.

Previously the animations array was statically resolved and then the
values were translated back when generating ngComponentDef.

PR Close #26322

packages/compiler/src/render3/view/api.ts

@@ -179,7 +179,7 @@ export interface R3ComponentMetadata extends R3DirectiveMetadata {
   /**
    * A collection of animation triggers that will be used in the component template.
    */
-  animations: {[key: string]: any}[]|null;
+  animations: o.Expression|null;
 }
 
 /**