Issue 83 bad hex value

Work around for #83 (closed). The NDS1 server is sending bad data on occasion. Catch the specific error, cycle the connection, and re-issue the command.

This also adds a new recording proxy that can record multiple concurrent input streams, boost filesystem as a build dependency (for the proxy), and vendors a current copy of the nlohmann json library (as the versions very widely between the LSC reference platforms).