feat(tree): typescript/strong typing of nodes

### Feature Description

Currently `*matTreeNodeDef` types the resulting variable as `any`:


### Use Case

>enable you to build web apps with confidence!

The lack of strong typing is really problematic for bigger projects, and it feels like a downgrade in developer experience compared to custom build trees.

Further motivation for this has been described in:

https://github.com/angular/components/issues/16273
https://github.com/angular/angular/issues/28731
https://nartc.me/blog/typed-mat-cell-def/
https://github.com/angular/components/issues/22290

Workaround copied from https://github.com/angular/components/issues/22290:
```ts
import { Directive, input } from '@angular/core';
import { MatTree, MatTreeNodeDef } from '@angular/material/tree';

@Directive({
selector: '[matTreeNodeDef]',
providers: [
{ provide: MatTreeNodeDef, useExisting: TypeSafeMatTreeNodeDefDirective },
],
})
export class TypeSafeMatTreeNodeDefDirective extends MatTreeNodeDef<
NoInfer
> {
readonly matTreeNodeDefTree = input.required>();

static ngTemplateContextGuard(
dir: TypeSafeMatTreeNodeDefDirective,
ctx: any,
): ctx is { $implicit: T; index: number } {
return true;
}
}
```

```diff
-
+
...
-
+
```

Comienza con los puntos de entrada MatTreeNodeDef, MatTree y matTreeNodeDef mostrados en el issue, y luego compara el workaround TypeSafeMatTreeNodeDefDirective enlazado y las discusiones referenciadas. Se considera terminado cuando la variable declarada por *matTreeNodeDef tiene un tipo fuerte sin requerir el workaround, y el uso documentado del árbol sigue funcionando.

Escrito por el modelo de indexación a partir del texto del issue.