Object-based wrapper for reporting

I'm trying to add some features to a reporting base class
such that all child reports can inherit the features. Besides
some standardization the main features added so far are
jQuery based sorting & styling and result caching.

The department and product movement reports have the
best commenting.

I realize "classlib2.0" is kind of ridiculous. I'm not entirely
happy with the module system I was tinkering with in "class-lib"
and it will go away eventually. In the long run I'd like the
backend class and plugin system to mimic the lane both for the
sake of consistency and because I think the lane model is
better.
ccReceiptView updates for Mercury transaction type naming conventions
Corrected Excel/CSV links for reports with no URL parameters
Added auto-linking for UPC values
Updated non-movement report
Linux unreliable solution
JQuery reports live, experimenting with prepared statements
Fix for sale price AND split price
Merge branch 'master' of https://github.com/CORE-POS/IS4C

# By Andy Theuninck
# Via Andy Theuninck
* 'master' of https://github.com/CORE-POS/IS4C:
  Fix for sale price AND split price
  JQuery reports live, experimenting with prepared statements
  Linux unreliable solution
  Corrected Excel/CSV links for reports with no URL parameters Added auto-linking for UPC values Updated non-movement report
  ccReceiptView updates for Mercury transaction type naming conventions
  Object-based wrapper for reporting