skip leading zeros even after decimal point in floatscan
skip leading zeros even after decimal point in floatscan

in principle this should just be an optimization, but it happens to
also fix a nasty bug where values like 0.00000000001 were getting
caught by the early zero detection path and wrongly scanned as zero.

chardi/musl,chardi/musl,chardi/musl