fix(mvux): Properties update might be deferred too long if dispatcher is under heavy stress

[dr1rrb]

fixes #2188

Bugfix

Properties update might be deferred too long if dispatcher is under heavy stress

What is the current behavior?

When a property change often, we wait for the dispatcher to have process the last update before fetching the next update from the bg thread.

What is the new behavior?

Updates are scheduled as soon as possible from the bg thread and de-duplicated if

PR Checklist

Please check if your PR fulfills the following requirements:

• Tested code with current supported SDKs
• Docs have been added/updated which fit documentation template. (for bug fixes / features)
• Unit Tests and/or UI Tests for the changes have been added (for bug fixes / features) (if applicable)
• Wasm UI Tests are not showing unexpected any differences. Validate PR Screenshots Compare Test Run results.
• Contains NO breaking changes
• Updated the Release Notes
• Associated with an issue (GitHub or internal)

[agneszitte]

@Mergifyio backport release/stable/4.1

[mergify]

backport release/stable/4.1

✅ Backports have been created

• #2262 fix(mvux): Properties update might be deferred too long if dispatcher is under heavy stress (backport #2250) has been created for branch release/stable/4.1 but encountered conflicts