feat(forms): introduce min and max validators

[sonukapoor]

This commit adds the missing min and max validators.

BREAKING CHANGE:

Previously min and max attributes defined on the <input type="number">
were ignored by Forms module. Now presence of these attributes would
trigger min/max validation logic (in case formControl, formControlName
or ngModel directives are also present on a given input) and
corresponding form control status would reflect that.

Fixes #16352

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular/blob/master/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• angular.io application / infrastructure changes
• Other... Please describe:

Does this PR introduce a breaking change?

• Yes
• No

[AndrewKushnir]

Initial presubmit to see if it breaks targets in g3 (+ global presubmit as well).

[sonukapoor]

@AndrewKushnir Thanks for the updated information. The changes and the refactor of the unit tests look good to me.

[jessicajaniuk]

reviewed-for: public-api

[mary-poppins]

You can preview 76d699b at https://pr39063-76d699b.ngbuilds.io/.

[AndrewKushnir]

Thanks for the review @atscott, great catch on string vs string|number type! 👍

I've pushed a fixup commit to adjust types. Could you please have another look when you get a chance?

[AndrewKushnir]

FYI, also started a new Global Presubmit.

[atscott]

reviewed-for: public-api

[AndrewKushnir]

The feedback was addressed and the most recent TGP run is successful, so I'm adding this PR to the merge queue.

@sonukapoor huge thanks for working on this feature and addressing all the comments 👍
Also thanks to the reviewers for provided feedback!

[AndrewKushnir]

Note to Caretaker: this PR is ready for merge, the TGP is "green" (only one unrelated build failure). It'd still be great to sync it in g3 as a separate/individual change to rollback easier if needed. Thank you.

[sonukapoor]

Always a pleasure @AndrewKushnir

[Airblader]

Does this affect applications which specify both the attribute and separately a corresponding validator in any way? Or would the validator then just run twice without noticable effects?

[AndrewKushnir]

@Airblader this change adds new min/max validators that would be invoked on <input type="number"> (when min/max attributes are present). This change does not block other existing (custom) validators from being executed.

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