fix: FluentNumberField's two-way data binding on Value Property does not update appropriately

[arazni]

This is extremely similar to #1450

🐛 Bug Report

In my web app, I have a component that takes a numeric input and divies a portion to a wallet and a portion to a stash. After a number is selected, a button triggers a command and this command also resets the value of the numeric field to 0.

Unfortunately, the numeric field does not respect the behavior of being reset to 0 by the button command.

💻 Repro or Code Sample

Download and run the code on this tag in dotnet8: https://github.com/arazni/blazor-fluent-ui-slider-bug/releases/tag/number-field-test

🤔 Expected Behavior

When I click a button that resets the two-way bound value of the NumberField to 0, the NumberField's Value property should change to 0 and the field should visibly appear to reset to 0.

😯 Current Behavior

When I click a button that resets the two-way bound value of the NumberField to 0, the NumberField's Value property stays at its current value and the field's visually apparent value stays at its current value.

💁 Possible Solution

Perhaps something very similar to how the Slider was fixed for #1450

🔦 Context

In my web app, I have a component that takes a numeric input and divies a portion to a wallet and a portion to a stash. After a number is selected, a button triggers a command and this command also resets the value of the numeric field to 0.

🌍 Your Environment

OS & Device: Windows 11 PC
Browser at least: Microsoft Edge and Mozilla FireFox
.NET 8.0.2 and FluentUI Version 4.4.1