let user know that there is a failing test case in corpus on startup

[0xalpharush]

If one stops and restarts the fuzzer and there is an assertion failure about to be shown from the initial corpus entries, it will appear as if fuzzing is stuck. Instead of showing the normal stats perhaps it would make sense to call it out explicitly in the logs/stdout

⇾ Initializing corpus
⇾ Setting up base chain
⇾ Initializing and validating corpus call sequences
⇾ corpus: health: 100%, sequences: 95 (95 valid, 0 invalid)
⇾ Fuzzing with 10 workers
⇾ fuzz: elapsed: 0s, calls: 0 (0/sec), seq/s: 0, coverage: 19
⇾ fuzz: elapsed: 3s, calls: 444 (147/sec), seq/s: 28, coverage: 19
⇾ fuzz: elapsed: 6s, calls: 444 (0/sec), seq/s: 0, coverage: 19
⇾ fuzz: elapsed: 9s, calls: 444 (0/sec), seq/s: 0, coverage: 19
⇾ fuzz: elapsed: 12s, calls: 444 (0/sec), seq/s: 0, coverage: 19
⇾ fuzz: elapsed: 15s, calls: 444 (0/sec), seq/s: 0, coverage: 19
⇾ fuzz: elapsed: 18s, calls: 444 (0/sec), seq/s: 0, coverage: 19
⇾ fuzz: elapsed: 21s, calls: 444 (0/sec), seq/s: 0, coverage: 19
⇾ fuzz: elapsed: 24s, calls: 444 (0/sec), seq/s: 0, coverage: 19
⇾ fuzz: elapsed: 27s, calls: 444 (0/sec), seq/s: 0, coverage: 19
⇾ fuzz: elapsed: 30s, calls: 444 (0/sec), seq/s: 0, coverage: 19
⇾ fuzz: elapsed: 33s, calls: 444 (0/sec), seq/s: 0, coverage: 19
⇾ fuzz: elapsed: 36s, calls: 444 (0/sec), seq/s: 0, coverage: 19
⇾ fuzz: elapsed: 39s, calls: 444 (0/sec), seq/s: 0, coverage: 19
⇾ fuzz: elapsed: 42s, calls: 444 (0/sec), seq/s: 0, coverage: 19
⇾ fuzz: elapsed: 45s, calls: 444 (0/sec), seq/s: 0, coverage: 19
⇾ fuzz: elapsed: 48s, calls: 444 (0/sec), seq/s: 0, coverage: 19
⇾ fuzz: elapsed: 51s, calls: 444 (0/sec), seq/s: 0, coverage: 19
⇾ fuzz: elapsed: 54s, calls: 444 (0/sec), seq/s: 0, coverage: 19
⇾ fuzz: elapsed: 57s, calls: 444 (0/sec), seq/s: 0, coverage: 19