fix: Avoid processing value change event due writing back of converted value

[TatuLund]

This is both a optimization by skipping duplicate validation round and avoids ConcurrentModificationExpectation being thrown certain corner cases.

Cherry pick from: vaadin/framework#12360

[anssit]

Please update the test based on review comments.

[vaadin-bot]

SonarQube analysis reported 8 issues

1. Binder.java#L945: Rename "binding" which hides the field declared at line 899.
2. Binder.java#L1018: Rename "binding" which hides the field declared at line 899.
3. Binder.java#L246: "public" is redundant in this context.
4. Binder.java#L253: "public" is redundant in this context.
5. Binder.java#L1957: Rename this generic name to match the regular expression '^[A-Z][0-9]?$'.
6. Binder.java#L2029: Rename this generic name to match the regular expression '^[A-Z][0-9]?$'.
7. Binder.java#L2812: Complete the task associated to this TODO comment.
8. Binder.java#L2826: Complete the task associated to this TODO comment.

[vaadin-bot]

Hi @TatuLund and @Artur-, when i performed cherry-pick to this commit to 8.0, i have encountered the following issue. Can you take a look and pick it manually?
Error Message:
Error: Command failed: git cherry-pick 57bfc5e
error: could not apply 57bfc5e... fix: Avoid processing value change event due writing back of converted value (#12183)
hint: after resolving the conflicts, mark the corrected paths
hint: with 'git add ' or 'git rm '
hint: and commit the result with 'git commit'

[vaadin-bot]

Hi @TatuLund and @Artur-, when i performed cherry-pick to this commit to 2.7, i have encountered the following issue. Can you take a look and pick it manually?
Error Message:
Error: Command failed: git cherry-pick 57bfc5e
error: could not apply 57bfc5e... fix: Avoid processing value change event due writing back of converted value (#12183)
hint: after resolving the conflicts, mark the corrected paths
hint: with 'git add ' or 'git rm '
hint: and commit the result with 'git commit'

[anssit]

Updated the label to 0.0.1 from 1.0.0. The bot was mistaken because of other changes in target branch.

[vaadin-bot]

This ticket/PR has been released with platform 22.0.0.beta2 and is also targeting the upcoming stable 22.0.0 version.