Fix exception due to responding with non-sent subprotocol

Recent version of Flowhub/noflo-runtime does not use "noflo" subprotocol
initially. The exception was hidden for a long time because in noflo-nodejs
one typically runs with captureExceptions: true