Filter and namespace the interaction data.

* Set up a table that says which events are noteworthy
* Save the number of emails a user has.
* All screens are namespaced under the screen namespace
* User interactions are saved under the user namespace
* window related events are under the window namespace
* Modify the hub to call global listeners before exact match listeners - this keeps events in the correct order in the store - the previous way had a new screen show up in the KPI event log before the "screen.cancel" event that triggered its display.

issue #1614
issue #1619