[bugfix] Align timing of interface coalescing and range update. #triv…

…ial (#847)

* fix SIMULATE_WEB_RESPONSE not imported #449

* Fix to make rangeMode update in right time

* This is for cases when CollectionNode is created in cell of another collectionNode, the interfaceState(say didEnterVisible) is not called as expected.

It's because interfaceCoalescing alter the time line and cause RangeController update before actual interface applied.

Source/ASDisplayNodeExtras.mm

@@ -70,7 +70,7 @@ extern ASInterfaceState ASInterfaceStateForDisplayNode(ASDisplayNode *displayNod
         // Directly clear the visible bit if we are not in a window. This means that the interface state is,
         // if not already, about to be set to invisible as it is not possible for an element to be visible
         // while outside of a window.
-        ASInterfaceState interfaceState = displayNode.interfaceState;
+        ASInterfaceState interfaceState = displayNode.pendingInterfaceState;
         return (window == nil ? (interfaceState &= (~ASInterfaceStateVisible)) : interfaceState);
     } else {
         // For not range managed nodes we might be on our own to try to guess if we're visible.