16544: fixed behaviour when some of JS validation rules making fields…

[VitaliyBoyko]

… required

Description

Fixed rules which make fields required:
max-words
min-words
range-words
letters-with-basic-punc
alphanumeric
letters-only
no-whitespace
zip-range
integer
vinUS
time
time12h
phoneUS
phoneUK
mobileUK
email2
url2
credit-card-types
ipv4
ipv6
pattern
validate-cc-number
validate-per-page-value-list

Fixed Issues (if relevant)

1. Some of JS validation rules making fields required #16544: Some of JS validation rules making fields required

Manual testing scenarios

1. Create a new module with form and field, or add a field to existing form
2. Set field validation, for example:
   <validation> <rule name="phoneUS" xsi:type="boolean">true</rule> </validation>
3. Field should not be required

Steps to reproduce

1. Don't fill out the field just submit a form

Expected result

1. The form is submitting as well

Contribution checklist

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• All automated tests passed successfully (all builds on Travis CI are green)

[magento-engcom-team]

Hi @VitaliyBoyko. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento-engcom-team give me test instance - deploy test instance based on PR changes
• @magento-engcom-team give me {$VERSION} instance - deploy vanilla Magento instance

For more details, please, review the Magento Contributor Assistant documentation

[magento-engcom-team]

Hi @VitaliyBoyko. Thank you for your contribution.
We will aim to release these changes as part of 2.2.7.
Please check the release notes for final confirmation.

Please, consider to port this solution to 2.3 release line.
You may use Porting tool to port commits automatically.