fix!(BigDecimalField): use custom logic instead of validated event

[vursen]

Description

The PR refactors BigDecimalField to make it trigger validation whenever a value-changed event is received from the client while the value still remains empty on the server, instead of relying on the validated event.

Depends on

• fix: ensure client-side value property is initialized #5590

Warning
It's a behavior altering change because it removes validation on blur when the value hasn't changed.

Part of #5537

Type of change

• Bugfix

[vursen]

I added tests for eager mode and they uncovered that there is an unexpected initial validation that is caused by the value-changed event that Polymer fires during the web component's initialization.

We've already encountered this kind of issue before: see #2878 that fixes it for DatePicker. In short, such value-changed events can be prevented by ensuring that the client-side value property is always initialized with an empty string when no custom value is provided.

[sonarqubecloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
15 Code Smells

No Coverage information
0.5% Duplication

Catch issues before they fail your Quality Gate with our IDE extension SonarLint

[vaadin-bot]

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