Framework: add error collector / logger with stack traces

[designsimply]

Raised by @gcorne

In order to gain insights into what if any errors our users are experiencing, we need to add some sort of error collector and logger.

@bazza suggested that the errors could be sent to logstash, which I think makes sense, although I don't know much about the capabilities of logstash. We also could do stuff like we have set up for Atlas that logs to IRC, bumps stats based on UA, and sends stack traces to a whitelist of email addresses. There are also third-party services for this sort of thing, but I think that we'll want to keep the data in house.

Some possible features:

1. Normalized stack traces
2. Include username and current URL to make reproducing easier
3. Support both exception catching and logging of specific errors that don't bubble up to window.onerror
4. Attempt to aggregate identical errors and ideally display them as a histogram so that it is easy to find the big errors
5. Try to separate fatal errors from less substantial errors
   ...

[stale]

This issue has been marked as stale because it hasn't been updated in a while. It will be closed in a week. If you would like it to remain open, can you please comment below and see what you can do to get things moving with this issue? Thanks! 🙏