Easier Cross-field-validation for mat-form-field/mat-error combinations

#### Feature Description

In reactive forms, cross-field validation requires the validation logic to be placed with the parent form instead of the individual control.
The existing feature works fine, however, changing the relevant `mat-form-field`(s) into an error-state to enable showing underlying `mat-error`(s) has to be done by calling the relevant `FormControl`'s `setErrors()` function.

However, with a directive, we need only to perform validation on the parent form and return `ValidationErrors`. The child controls can themselves detect whether they should go into error-state or not, and the developer need not worry further about it.

First, we run a normal validator function on the form that does nothing but return `ValidationErrors`. Then, we pass the key(s) of the error(s) for which we want cross-validation, to the custom directive.
Please note how the `mat-error`'s `*ngIf` depends upon the error-set of the `FormControl`, just like in normal validation, although it would still work if it depended on the error set of the parent `FormGroup` (which is what we do currently).
```

Range Start

Value must be less than End

```

#### Use Case
Developer convenience and ease of use. Brings more consistency between normal validation and cross-validation. Allows child controls to 'inherit' some user-specified errors of the parent on `valueChanges`.

#### StackBlitz
https://stackblitz.com/edit/angular-cross-validation-directive

Comienza con el ejemplo de StackBlitz enlazado y revisa cómo interactúan actualmente el formulario padre reactivo, los FormControls secundarios, mat-form-field y mat-error. Se considera terminado cuando una directiva pueda recibir las claves de error seleccionadas del formulario padre, exponerlas en los controles secundarios relevantes y permitir que mat-error use el estado de error del control secundario sin llamadas manuales a setErrors().

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