Add SiteStats ribbon for Lessons tool activity

I'm not 100% sure whether to report this here, but the Statistics->Lesson Pages section isn't displaying any meaningful statistics for us. On a test site, it reported 2 hits from a few months ago (not recording any current activity), until I deleted a whole bunch of unlinked Lessons pages, after which it reported -505 pages (see the screenshot). catalina.out isn't showing any exceptions, but something is clearly rotten in the state of Statistics. This is on Sakai 11.4 on Ubuntu 14.04 with its bundled MySQL (5.5.58).

Open

This isn't working in Oracle and causing database stacktraces. I've opened https://sakaiproject.atlassian.net/browse/SAK-30838#icft=SAK-30838

PR submitted in https://github.com/sakaiproject/sakai/pull/1254

From Laura Gekeler:

Site Statistics has a ribbon for Resources and identifies each resource by its original file name, which is very helpful, along with the number of access. There are tabs to sort the data By User, By Date, By Resource (name). It's even exportable. There are some limitations however. It would be nice if those limitations didn't exist, and certainly we wouldn't want to duplicate the limitations to the Lessons tool just because they exist.

Limitations on Site Statistics, Resources:

1. If Students are enrolled at the roster level, but not the site itself, their activity isn't recorded (This is true in ND's Sakai 10.2 environment).
2. The Export feature does not export all the data, but only the arrangement of the tab one is under. This means the export does not serve as a method by which an Instructor could perform further analysis. The better arrangement would be to be able to export rows which contain each action, per date/time, on resource title, by EID, in Role X.

As we continue to tweak existing tools, we need to ensure we do so in a way which is consistent with a roadmap toward true learning analytics and a 3rd party LTI Dashboard presented in each site. Eventually activity data will be reposed outside the LMS, but the way that it is aggregated, stored, displayed in dashboards and reported today in Sakai can move toward that target (or at least not move counter to that target!).

I'm going to start having a look at this on Oxford's behalf, just the gathering of the lessonbuilder events initally, no UI stuff.