Use nativeEvent.layout in onLayout, instead of buggy measureInWindow

[JelteF]

On Android with Expo (and its default translucent statusbar) the touchesTop
detection is incorrect. This is because measureInWindow has a bug that makes
its behaviour inconsistent with other platforms:
facebook/react-native#19497.

This PR replaces the usage of measureInWindow with the use of
nativeEvent.layout (which is the workaround provided in the issue linked
above). This makes touchesTop detection work for android correctly so
forceInset={{ top: 'always' }} doesn't have to be provided anymore.

[brentvatne]

this approach will not work for the reason described in comments. if you can provide a repro case for the bug you're encountering it'll help us to examine other solutions!

[brentvatne]

we need to pass the info var through here. i'd call it e or event instead, also. to see why it's necessary to pass it through have a look at https://snack.expo.io/@notbrent/thrilled-pizza - run it and then look at logs, you'll see this:

[brentvatne]

this will give the x and y relative to the container, not the x and y relative to the entire window. we need to know the x/y relative to the window because that's the only way to know if the container overlaps with a safe area. again run https://snack.expo.io/@notbrent/thrilled-pizza and notice the logs for "nested" show x/y of 0,0 despite it not being in the top left of the screen.

[JelteF]

Sorry for not responding to this earlier. The repro case is simply:

• use an android device with Expo (create-react-native-app)
• put anything at the top of the screen (for instance a element)
• see that the status bar is on top of the text