refactor(schematics): constructor checks should respect assignability

[devversion]

Reworks the constructor signature check rule to take advantage of the TypeScript pre-emit diagnostics. This is necessary because there is no public API to check the relation of two types (e.g. checking if the super-call arguments are assignable to the actual constructor parameter signature)

This now means that the constructor checks respect type assignability (e.g. it won't throw incorrectly if a developer does something like:

class ExtendedPlatform extends Platform {}

new NativeDateAdapter(a, new ExtendedPlatform(...))

// Similarly it doesn't fail if an object is assignable to an interface (previously would fail):

new RippleRef(a, b, {persistent: true})

[jelbourn]

LGTM

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