calciteInputInput returns 000000, should probably not display this

calciteInputInput returns valid numbers 1 and 5, but it should not allow a display like this

calciteInputInput returns 03
Start with a value of 0. Then type in a 3 after the 0. The input box correctly updates to just 3.

1.
@AdelheidF @jcfranco Should we diverge from how the native <input type="number"> element works by truncating 00000 to just 0? In a native number input, it allows multiple zeros, both in the display and the stored value at form submission time:


I don't see where these zeros would ever be useful for an input field of type number.
Tested with the latest next.226 (from 11 days ago!)
I can no longer enter 1.... or 1,,,,, so that part is good.
Waiting on a newer next release to test 0000.
Tested now with next.227 and 0000 is good too.