more issue #598 - add test and fix for other places where exceptions leak out of JWCrypto and cause 500 errors rather than 200 failure responses.

the verifier is more helpful if you leave off content-type headers, also did you know we support application/json?  closes #643

implement graceful process shutdown, and clear logging as to the reason why processes are terminating.  include winston handling of uncaught exceptions.  this all goes into a library that all of our processes use.  closes #529

in production (dev/beta/prod) use a more conventional logging format that includes timestamps.  closes #234

remove CORS from repository.  In-repo example now properly forwards requests to verifier from server.  closes #245

implement graceful process shutdown, and clear logging as to the reason why processes are terminating.  include winston handling of uncaught exceptions.  this all goes into a library that all of our processes use.  closes #529

in production (dev/beta/prod) use a more conventional logging format that includes timestamps.  closes #234

fix undefined reference (crash) in verifier after verification failure.  closes #523.  introduced in issue #82.

include full origin (inc. scheme) in generated assertions.  To preserve compatibility, allow the rp to omit scheme in post data, and subsequent to verification, return whatever the rp sent us.  issue #82

added issuer back to verifier response, using now hostname only of issuer, since that's all we will have for primaries, e.g. @gmail.com

find instances of console.log() and send them to the logger instead, when running under dev harness also route to console.  issue #169

rather than imposing restrictions on structure of logged objects we should make all required fields proper parameters that are obvious upon inspection of the signature of the log function. issue #168