fix: Strongly typed number field starts at min/max instead of 0 in Blazor

[vnbaaij]

🐛 Bug Report

In the 2.0 WC release PR #5289 has been merged in. This has restored working of the up/down controls (:thumbsup: ) but it also introduced a new (and unwanted) effect in the Blazor <FluentNumberField> component.

Because we can strongly type components in Blazor, we need to supply Min and Max parameters to make sure the value stays within the designated type of the field. This now has the effect that when a field is empty, pressing Up(Down) shows the Min(Max) value instead of using 0 as a start point.

💻 Repro or Code Sample

Run the FluentServerSample from the fast-blazor repo and go to the Number test page.

🤔 Expected Behavior

Empty number field should start from 0 when no initial value is supplied

😯 Current Behavior

This field holds a number of type integer (int). No initial value is set. Clicking 'Down' control shows maximum int value.. Should start at 0 and show -1