Add useHandleRef as a lighter alternative for useAnimatedRef

[gaearon]

We use useAnimatedRef in a bunch of places just to get the measurements with measure. This is unfortunate because it contains two shared values, one of which stores an internal React node. I'm not sure whether that node goes through the serialization mechanism but the profiler was showing some overhead associated with each useAnimatedRef component.

In this PR, I'm taking just the part that we actually need — reading the component's internal handle. I'm doing the same thing findNodeHandle does except for the slow codepath we don't need (which only triggers for class components). I put that code inline so it's clearer how it works.

On the measure side, I realized that all Reanimated's measure() really wants is a function that returns the handle. (The useAnimatedRef API plays a trick here where it doubles as both a React callback ref which receives the component and as a function that measure can call to get the value.) So I'm just passing () => handle for that case.

I've also replaced <Animated.View> with plain <View> to reduce overhead since there's no need for Reanimated there at all.

Test Plan

Verify you're still able to expand/collapse images:

• Single image (AutoSizedImage)
• Gallery
• User avatar
• Feed avatar

handle.mov

andr.mov

Before

ImageLayoutGridInner and AutoSizedImage were sticking out as having a bunch of self-time in traces.

After

ImageLayoutGridInner and AutoSizedImage no longer take disproportionate time in traces.

[github-actions]

Old size	New size	Diff
8.05 MB	8.05 MB	336 B (0.00%)

---

[mozzius]

Tested on iOS+Android, lgtm