AFJSONRequestOperation processes JSON before isFinished set

The issue here was the `AFJSONRequestOperation`'s `responseJSON` method computed its result lazily. Therefore, if called from multiple threads, things would blow up. The solution proposed in this PR is to process the JSON prior to marking the operation finished, on the thread on which the connection finishes. This means that callers of `responseJSON` are not burdened with processing the JSON, and that property can be a simply read-only property.

Long-term, we're going to need to replace our use of AFNetworking 1.0. We may do this next milestone as we move towards using background transfer for backup/sync.

PTAL @floatplane @DawnWright @charlesmchen 
Instead of adding an `operationWillFinish` method, would a simpler change of just calling `processResponseJSON` before invoking the success block work? Admittedly I don't have a lot of context here: I can't tell whether this success block is called before or after the `AFNetworkingOperationDidFinishNotification` is sent.