Improved skipping commits

[michalmaka]

Summary

During investigation of race between RN and reanimated shadow tree committing I've noticed that if JS thread commits a new tree (triggering pleaseSkipReanimatedCommit) after starting commit from reanimated, the latter commit may cause JS commit failures.

What's more, additional calls to shouldReanimatedSkipCommit result in avoiding CPU consuming copy operations on nodes and thus seems to work more performant.

I added those checks just before each operation handling and just after full commit.

Chessboard example seemed to work a bit faster that without those changes. I used also profiler and in overall CPU spends less time in ShadowTree.

NOTICE ⚠️
This change requires change in RN codebase. PR has been submitted facebook/react-native#38715

Test plan

Check performance of e.g. chessboard example.

[efstathiosntonas]

@michalmaka you're on fire! 💪 🔥

[tomekzaw]

⚠️ Wait for facebook/react-native#38715

[efstathiosntonas]

@tomekzaw I've asked rn team to pick it on 0.72.4 reactwg/react-native-releases#83 (comment)

[efstathiosntonas]

Hey folks, this was picked from rn team for 0.72.4. Thank you for your hard work

[tomekzaw]

As discussed internally, let's add #ifdefs for RN version not to change the behavior of 0.72.x since this PR requires things which were added in 0.72.4.

[tomekzaw]

Thanks for this PR!