bug: stat panics with --printf

Hi, uutils mainteners stat have some problems like printf, with the --printf, that is my tries of all previous isses and some work against stat --printf

relunsec@relunsec:~/software/coreutils/target/debug$ ./stat --printf="%111111.1d" f

thread 'main' (90490) panicked at src/uu/stat/src/stat.rs:113:36:
Formatting argument out of range
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
relunsec@relunsec:~/software/coreutils/target/debug$ ./stat --printf="%111111c" f
?relunsec@relunsec:~/software/coreutils/target/debug$ ./stat --printf="%.100000d" f

thread 'main' (90794) panicked at src/uu/stat/src/stat.rs:669:33:
Formatting argument out of range
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
relunsec@relunsec:~/software/coreutils/target/debug$ ./stat --printf="%.100000f" f

thread 'main' (90938) panicked at src/uu/stat/src/stat.rs:719:33:
Formatting argument out of range
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
relunsec@relunsec:~/software/coreutils/target/debug$ ./stat --printf="%.100000d\n" f

thread 'main' (90961) panicked at src/uu/stat/src/stat.rs:669:33:
Formatting argument out of range
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
relunsec@relunsec:~/software/coreutils/target/debug$ ./stat --printf="%.111111s" f

thread 'main' (91409) panicked at src/uu/stat/src/stat.rs:587:33:
Formatting argument out of range
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
relunsec@relunsec:~/software/coreutils/target/debug$ ./stat --printf="%.111111a" f

thread 'main' (92238) panicked at src/uu/stat/src/stat.rs:694:33:
Formatting argument out of range
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
relunsec@relunsec:~/software/coreutils/target/debug$ 

only one is not panicked the rest yes

Start in src/uu/stat/src/stat.rs at the reported locations around lines 113, 587, 669, 694, and 719. Reproduce the failures with the listed stat --printf formats, then trace how large widths and precisions are handled. Done means these inputs no longer panic and retain appropriate stat --printf behavior.