One syntax for all types of mat-icon

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

Feature request

#### What is the expected behavior?

Changing between ligature-based and class-based icon specification shouldn't be a huge chore.

#### What is the current behavior?

To use ligature-based icons, I write `home`. If I want to change from an icon font to a font set that uses CSS classes to pick a glyph, I'd have to change each component by hand to something like ``.

#### What is the use-case or motivation for changing an existing behavior?

I've created a large application that uses dozens of `mat-icon` components, and would like a simple method of changing how they're rendered. Ideally, I'd be able to call something like `setDefaultFontSetClass` once and have all icons (that don't explicitly set a `fontSet` attribute) change their source.

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

N/A, mat-icon has always behaved like this

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

It would be great if either the `fontIcon` attribute or the component content could be used to select a glyph regardless of how the font set is provided, but I'd be happy to be told to just always use one or the other, as long as switching between types of font set using the icon registry is straightforward.

Beginne damit, das Verhalten der mat-icon-Komponente und die im Issue beschriebenen APIs der Icon-Registry zu lesen, wobei du dich darauf konzentrierst, wie Ligaturinhalt, fontIcon und fontSet ausgewählt werden. Die Aufgabe ist abgeschlossen, wenn eine große bestehende Anwendung über eine einzige Standardkonfiguration zwischen ligaturbasierten und klassenbasierten Icon-Quellen wechseln kann, ohne jede mat-icon-Verwendung bearbeiten zu müssen.

Vom Indexierungsmodell aus dem Issue-Text verfasst.