Setting a single formControl to Untouched does not reset the error css state

#### Bug, feature request, or proposal:
Bug

#### What is the expected behavior?
Don't use mat-form-field-invalid, but use the native angular core css classes ng-invalid
Because mat-form-field-invalid does not get removed when setting a single formControl to untouched

#### What is the current behavior?
mat-form-field-invalid does not get removed when doing markAsUntouched

#### What are the steps to reproduce?
Providing a StackBlitz reproduction is the *best* way to share your issue.

StackBlitz starter: https://goo.gl/wwnhMV

On every simple form

#### What is the use-case or motivation for changing an existing behavior?
Material uses it's own mat-form-field-invalid css class instead of the angular core css classes, this makes error. This is a wrong design

#### Which versions of Angular, Material, OS, TypeScript, browsers are affected?
newest versions

#### Is there anything else we should know?

Start with the linked StackBlitz reproduction and trace how markAsUntouched affects the Material form-field error state versus Angular's native form-control classes. Confirm the behavior on a simple form, then verify that marking one control untouched removes the corresponding invalid styling without changing other controls.

Written by the indexing model from the issue text.