fix(forms): improve types of directive constructor arguments

[AndrewKushnir]

Prior to this change, the validators and asyncValidators fields of a few Forms directives
were typed as any[]. This commit updates the types and makes them consistent for all directives
in the Forms package.

BREAKING CHANGE:

Directives in Forms package used to have any[] as a type of validators and asyncValidators
arguments in constructors. Now these arguments are properly typed, so if your code relies on
directive constructor types it may require some updates to improve type safety.

PR Type

What kind of change does this PR introduce?

• Bugfix

Does this PR introduce a breaking change?

• Yes, see description above
• No

[AndrewKushnir]

Initial presubmit + Global TAP run (internal-only links).

[jelbourn]

LGTM

Reviewed-for: public-api

[AndrewKushnir]

Just a quick update: this change has limited impact in Google's codebase (only 1 target was affected) and the tests went well in the ngcc-validation repo. This is still a breaking change, but its impact on user's code is minor.

[petebacondarwin]

Reviewed-for: public-api

[IgorMinar]

Thanks for verifying the impact of this breaking change. I think most of the breakages will be within the application (as opposed to 3rd party library) code, so developers should be able to resolve them during an upgrade along with other breakages caused by improved TypeScript compiler checks.

LGTM!

Reviewed-for: public-api

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