Add fuzz testing #48
Description
Experience with #46 has shown that as well as need for #47, it is also necessary to validate unexpected input performs as expected on Linux, Mac, and Windows and does not crash or leak. (though the latter would require a running memory sanitizer as well) In my dealings with developing #46 I've discovered numerous accidental bugs that could cause the program to crash, it is unlikely for there to be memory leaks as I avoid non-RAII structures but I cannot be completely sure of this. A fuzzer test is distinct from unit testing as well since unit testing lays out expected results from both valid and invalid input, whereas a fuzzer runs in an attempt to produce invalid inputs that should crash the program demonstrating unhandled previously unknown edge cases. (aka bugs in the parser)