Updates to Consumer Status Report

- Removed start_date, end_date and hours parameters.
- Added on_date parameter
- only include compliance snapshots from consumers that we
  not deleted on/before target date (on_date)
- Cleaned up test data a little to make it more readable.
Added post filter when looking up compliance snapshots
Update on_date report param info
ConsumerHandler now stores correct Consumer UUID

Handler was storing the id of the Consumer, and not the UUID
when handling created/deleted events.
Fixed filters when looking up deleted consumers

- findByUuid could not use findByKey as it is looking for an ID object.
  Used a straight lookup instead.
- use 'owner.key' when filtering deleted consumers.
- added some tests around the curator.
- added some convenience methods to Consumer.
Rename method since the name no longer fits
Lookup active consumer uuids instead of deleted ones.
Pull uuid from correct event target
Merge pull request #701 from candlepin/mstead/consumer-status-report-fixups

Consumer Status Report Fixes
Move REST exceptions to common package

Allows their use in gutterball resources.
Add a friendly description for compliance event.
Merge pull request #705 from candlepin/dgoodwin/compliance-description

Add a friendly description for compliance event.
Fixed path issue for API lib.
Merge pull request #706 from candlepin/mstead/script-path-fix

Fixed path issue for API lib.
Merge pull request #704 from candlepin/wottop/gutterball-rest-exceptions

Move REST exceptions to common package
gitignore - ignore files having to do with ruby version managers
use TC var for service as well as dirs
Small fixes to the performance data script.

- Randomize the installed products for a consumer
- Fixed issue where the pools would be created as future pools.
Fixed max result size issue in report

Fixed an issue with the Consumer Status Report where an error
would be thrown if the result set reached a certain size.

First query for the IDs of the latest compliance snapshots
and then do a final lookup by id using find. The find method
does not have a data size limit here since it returns a DB
cursor to the results.

While doing this is not that pretty, it did not seem to have
much of an impact on performance as a lookup by a set of IDs
is pretty quick.

Indexes were also added to the consumer and compliance collections,
however, this did not seem to improve query performance all that
much.
Merge pull request #710 from candlepin/ckozak/gutterball_tomcat_service

use TC var for service as well as dirs