refactor(ivy): remove def.attributes in favor of the elementHostAttrs instruction (#28089)

Up until this point, all static attribute values (things like `title` and `id`)
defined within the `host` are of a Component/Directive definition were
generated into a `def.attributes` array and then processed at runtime.
This design decision does not lend itself well to tree-shaking and is
inconsistent with other static values such as styles and classes.

This fix ensures that all static attribute values (attributes, classes,
and styles) that exist within a host definition for components and
directives are all assigned via the `elementHostAttrs` instruction.

```
// before
defineDirective({
  ...
  attributes: ['title', 'my title']
  ...
})

//now
defineDirective({
  ...
  hostBindings: function() {
    if (create) {
      elementHostAttrs(..., ['title', 'my-title']);
    }
    ...
  }
  ...
})
```

PR Close #28089

packages/core/src/render3/styling/class_and_style_bindings.ts

@@ -75,7 +75,7 @@ export function initializeStaticContext(attrs: TAttributes) {
  * @param directive the directive instance with which static data is associated with.
  */
 export function patchContextWithStaticAttrs(
-    context: StylingContext, attrs: TAttributes, directive: any): void {
+    context: StylingContext, attrs: TAttributes, startingIndex: number, directive: any): void {
   // If the styling context has already been patched with the given directive's bindings,
   // then there is no point in doing it again. The reason why this may happen (the directive
   // styling being patched twice) is because the `stylingBinding` function is called each time
@@ -89,7 +89,7 @@ export function patchContextWithStaticAttrs(
     let initialStyles: InitialStylingValues|null = null;
 
     let mode = -1;
-    for (let i = 0; i < attrs.length; i++) {
+    for (let i = startingIndex; i < attrs.length; i++) {
       const attr = attrs[i];
       if (typeof attr == 'number') {
         mode = attr;