Fuzz SCSI/NVMe message processing

[Ralith]

We want to ensure that no SCSI input, no matter how malformed, can cause the translation library to invoke undefined behavior. A good insurance measure for this is fuzzing, which will attempt to randomly generate dangerous inputs. libFuzzer and AFL are two particularly good fuzzers worth considering.

We should also be robust to unexpected NVMe inputs. Malicious data is less likely to come from that direction, but complex attacks (or unfortunate coincidences of bugs) can violate such assumptions, and misbehaving hardware is always a possibility.

Much of the challenge might be working out graceful integration with the build system. https://github.com/googleinterns/bazel-rules-fuzzing may be of interest, but may not be sufficiently mature for use.