Fixed Bug in Websockets Problem

There is a bug in the websockets problem, where the verify script shows a blank string for both the actual and expected results. This means that any solution which connects to the server will be verified, regardless of the information sent to the server. I fix this (for the most part) by providing opts.a and opts.b as additional, possible arguments when the compare() function is called from within /bin/verify.js. It will still pass if extra lines are provided or the \n is left off, but at least it checks for SOMETHING now. In all of the other problems, opts.a and opts.b are falsy (null) so for those, verify.js should fall back to the old behavior.