fix(@schematics/angular): set explicit type in library schematic

[crisbeto]

Explicitly sets an empty type when the library calls into the component schematic for a few reasons:

1. The type for classes mostly makes sense in an application contenxt. E.g. libraries are unlikely to have guards.
2. The generated component is there primarily as an example and library authors are likely to either delete it or modify it to match their expected public API.
3. It ensures that the generated files remain correct if the component schematic ends up inheriting the type from the workspace.

[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.}