refactor!: ensure initial validation with constraints and value

[vursen]

Description

This PR ensures initial validation for email-field when it has constraints and value. Unlike other components, in the case of email-field, it means that the initial validation will always happen initially when it has value since there is a default pattern constraint.

In case the user wants to control invalid manually, the default pattern can be disabled by providing a custom empty pattern:

<vaadin-email-field value="user@example.com" pattern="" invalid></vaadin-email-field>

Warning
It is a kind of breaking change because manual invalid control is no longer possible when the field has a value unless the user disables the default pattern explicitly.

Extracted from #4386

Part of #4371

Type of change

• Refactor

Checklist

• I have read the contribution guide: https://vaadin.com/docs-beta/latest/guide/contributing/overview/
• I have added a description following the guideline.
• The issue is created in the corresponding repository and I have referenced it.
• I have added tests to ensure my change is effective and works as intended.
• New and existing tests are passing locally with my change.
• I have performed self-review and corrected misspellings.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[vaadin-bot]

This ticket/PR has been released with Vaadin 23.2.0.rc1 and is also targeting the upcoming stable 23.2.0 version.