ensure errors are logged in ExceptionHandler [no ticket; risk: low]

[davidangb]

in the global ExceptionHandler for all routes, add a statement to log the exception in the catch-all case.

The global ExceptionHandler otherwise swallows these errors if they're not manually logged. In the case of some akka errors, such as when akka rejects a payload for being too big, this meant the exception was silently discarded.

See also broadinstitute/rawls#1316

---

Have you read CONTRIBUTING.md lately? If not, do that first.

I, the developer opening this PR, do solemnly pinky swear that:

• I've followed the instructions if I've made any changes to the API, especially if they're breaking changes
• I've updated the RC_XXX release ticket with any manual steps required to release this change
• I've updated the FISMA documentation if I've made any security-related changes, including auth, encryption, or auditing

In all cases:

• Get two thumbsworth of review and PO signoff if necessary
• Verify all tests go green
• Squash and merge; you can delete your branch after this unless it's for a hotfix. In that case, don't delete it!
• Test this change deployed correctly and works on dev environment after deployment

[coveralls]

Coverage decreased (-0.05%) to 64.359% when pulling 5f897eb on da_logHandledExceptions into 02d25a0 on develop.

[davidangb]

error in fiab-start that looks transient:

ERROR: for martha-proxy  Cannot start service martha-proxy: driver failed programming external connectivity on endpoint firecloud_martha-proxy_1 (e0085ec73dc022779662dee17dd1f528bc40d26642e8fcafbe52e207b4ec901d): Error starting userland proxy: listen tcp 0.0.0.0:32800: bind: address already in use

jenkins retest.

[ungwudik]

Same comment as in the other PR https://github.com/broadinstitute/rawls/pull/1316/files#r526327849