refactor(compiler): Ingest host attribute bindings in template pipeli…

…ne (#51188)

Host property bindings beginning with `attr.` should have `Attribute` binding kind, and result in an `attribute` instruction.

This should really be handled in the parser in the future.

PR Close #51188

packages/compiler-cli/test/compliance/test_cases/r3_view_compiler_bindings/host_bindings/TEST_CASES.json

@@ -56,8 +56,7 @@
             "host_attribute_bindings.js"
           ]
         }
-      ],
-      "skipForTemplatePipeline": true
+      ]
     },
     {
       "description": "should support host attributes",

packages/compiler/src/template/pipeline/src/ingest.ts

@@ -55,6 +55,8 @@ export function ingestHostBinding(
   return job;
 }
 
+// TODO: We should refactor the parser to use the same types and structures for host bindings as
+// with ordinary components. This would allow us to share a lot more ingestion code.
 export function ingestHostProperty(
     job: HostBindingCompilationJob, property: e.ParsedProperty): void {
   let expression: o.Expression|ir.Interpolation;
@@ -65,9 +67,14 @@ export function ingestHostProperty(
   } else {
     expression = convertAst(ast, job);
   }
+  let bindingKind = ir.BindingKind.Property;
+  // TODO: this should really be handled in the parser.
+  if (property.name.startsWith('attr.')) {
+    property.name = property.name.substring('attr.'.length);
+    bindingKind = ir.BindingKind.Attribute;
+  }
   job.update.push(ir.createBindingOp(
-      job.root.xref, ir.BindingKind.Property, property.name, expression, null, false,
-      property.sourceSpan));
+      job.root.xref, bindingKind, property.name, expression, null, false, property.sourceSpan));
 }
 
 export function ingestHostEvent(job: HostBindingCompilationJob, event: e.ParsedEvent) {}