Notification expectations support verifying the userInfo. Added tests for userInfo and cardinality verification of notifications. All notification expectations must now be fully specified, with a name, a sender, and a userInfo dictionary.

Rationale: How could we distinguish a nil userInfo param indicating we don't care from an expected nil?. A hamcrest HC_anything() matcher used inside LRNotificationExpectation init methods doesn't seem right, and adding a BOOL to indicate if we should care about userInfo doesn't seem worth it, either.