[Issue #115] Allow subentities to be specified from API response

AFIncrementalStore assumed a one-to-one mapping of API endpoint to entity. However, an API like an activity stream might return several different types of data that should be represented by subentities. With this commit, the API client can map entities to the representations of those entities. The same can be done with relationship representations.

This change should be backwards compatible for those who have not overridden private methods and are using AFRESTClient. For anyone rolling their own client, the following methods are now required:

representationsByEntityOfEntity:fromResponseObject:
representationsByEntityForRelationshipsFromRepresentation:ofEntity:fromResponse:

And these methods are now optional:

representationOrArrayOfRepresentationsOfEntity:fromResponseObject:
representationsForRelationshipsFromRepresentation:ofEntity:fromResponse:
Fixed context/thread error

- Fixed context/thread error
- Workaround on recursive inserts

Signed-off-by: Darren Ehlers <me@darrenehlers.com>
Added more thread/context performBlocks

Signed-off-by: Darren Ehlers <me@darrenehlers.com>
Reverted MergeChanges flag

* I'm reverting this for the time being while working thru the way the CoreData contexts are supposed to work, and improving the setup.

Signed-off-by: Darren Ehlers <me@darrenehlers.com>
Fixed deadlock problem, adding check for main thread before performing performBlock calls

Signed-off-by: Darren Ehlers <me@darrenehlers.com>
Merge pull request #1 from tableproject/fixed-deadlock-problems

Fixed deadlock problems