Always give stack traces for error logs

[braydonf]

This update will log stack traces for errors (e.g. this.logger.error).

[tynes]

@chjj Can you publish the latest changes to blgr so that this PR can include a blgr npm version in the package.json instead of referencing a specific commit?

The update to blgr in particular is this commit:
bcoin-org/blgr@f8e21fc

It is so that stack traces are logged for errors, it makes debugging production errors much easier

[braydonf]

I have another solution at bcoin-org/blgr#5 that doesn't need the changes made to pool.js.

[braydonf]

Okay, I've updated, and now changes to net/pool.js are not necessary.

[nodech]

@braydonf Can you update all other dependencies as well ?

Current deps are not compatible with node-12.

[braydonf]

Can be done in another PR, addressing the logger stack trace issue with this one (which is now mostly bcoin-org/blgr#5).

[braydonf]

Until blgr is released, the stacks should be available in debug.log, for anyone that finds this and needs to find the stack. Unfortunately there isn't a sha512 integrity hash for git referenced dependencies, and is without semver.