Remove most remaining usages of TypeScript mixins

[crisbeto]

These changes remove all the remaining usages of mixinColor, mixinDisabled, mixinDisableRipple and mixinTabindex in favor of using input transforms and host bindings. There are still some usages of mixinErrorState and mixinInitialized that have to be migrated separately.

I've made this refactor, because:

1. We need to switch away from mixinColor, because it uses direct DOM manipulation. This is problematic for future hydration and SSR efforts.
2. Mixins add a lot of boilerplate, increase the prototype chain and can be difficult to reason about. mixinDisabled, mixinDisableRipple and mixinTabindex were only used for input coercion which can be replaced with input transforms.

[mmalerba]

We should consider deprecating and removing these mixins in the future

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}