Include changes to Notes, Relationships, Tags and Groups in contact logging reports. Make logging summary instance reserved. Remove logging detail from reports listing.

Log work on this issue to Bluebird: http://senatedev.senate.state.ny.us/issues/show/5260

1. Extend Contact Logging Summary report to include changes to Notes, Relationships, Tags and Groups (refer to attached screenshot for prototype)
1.1 Add Log Type column to the report (col 1 in listing) - displayed by default. Log types are Contact, Group, Note, Relationship, Tag. Contact log type is for all changes to contact record, email, phone, address, contact custom fields.

1.2 For Notes and Relationships - display Insert or Delete as applicable. For updates, include link on Update in action column to "details" as we do with other contact data.

1.3 For tags and groups, action column displays "Added" or "Removed". Append tag or group name surrounded by square brackets to contact name in "Altered Contact" column. No details link is needed. (see attached prototype screenshot)

1.4 Add Log Type filter to summary report

1.5 Expose "Filters" on the contact "Change Log" tab - including the new Log Type filter (but excluding the "Altered Contact" filter - since that's determined by the contact context). Changes to these filters affect only the current display in the contact tab. Default values are acquired from the Contact Summary report instance linked to the Change Log tabs.

2. When we create the "special" instance of the Logging Summary report (which happens when Logging is enabled) - set the is_reserved flag for that instance to TRUE. This prevents un-authorized users from modifying the default display columns and filters (which would affect everybody's Change Log tab).

3. The class file which handles display of each logging detail item should never be accessed directly - and therefore should not be exposed in the Report Listings. Brian's suggestion is to modify the class structure so this "page" is not part of the reports hierarchy. This seems to make sense since CRM_Report_Form_Logging_Detail isn't a full report, and basically extends CRM_Logging_ReportDetail. Bottom line is that we shouldn't create a Logging Detail report instance when logging is enabled - but rather link to a URL that invokes the details page. Page title should also change to "Logging Details".