Change the RKPropertyInspector cache writeback to use dispatch_barrier_sync instead of _async.  Due to the change in #2095 this code is now much more likely to be called from an +initialize method, and the async call at that point is dangerous, potentially leading to deadlocks with ObjC runtime locks (see #2101).  Keeping everything on the same thread should avoid deadlock possibilities.  It may even be better anyways, as any object mapping with more than one property will immediately call back to get the attributes for the same class so it would be waiting anyways, and the async would just add potential thread context switches on top of a simple sync call.
Merge pull request #2103 from carllindberg/2101-RKPropInspectorSync

Change the RKPropertyInspector cache writeback to use dispatch_barrier_sync