Incorporate the Big List of Naughty Strings into the test suite

[ssokolow]

Given that this handles what could be untrusted input, I'll want to approach edge-case handling from both sides.

I've already manually audited most of the code paths under my control, but I also want to cover known problem cases (as embodied in the Big List of Naughty Strings) to improve the chances of catching less obvious-to-me problems. (eg. problems rooted within modules I depend on)