Autoworkletize callbacks in Layout Animations

[tjzel]

Summary

Currently we support auto-workletizing callbacks with method chaining for react-native-gesture-handler:

Gesture.Tap().onBegin(() => {
  // will be automatically workletized
  ...
});

This pull request adds similar functionality to Layout Animations and their withCallback method so the worklet directive is no longer necessary.

FadeIn.duration(400).withCallback(() => {
  // will be automatically workletized now
  ...
});

Test plan

A new test suite was added to plugin's tests.

[piaskowyk]

I think we need also tests for class instance, for example - new FadeIn().withCallback() and for longer chaining like - FadeIn.duration().springify().withCallback(), FadeIn.duration().withCallback().springify()

[tjzel]

I don't think tests with new keywords are necessary. Moreover, I think they would be misleading as it's not a case that's in any way considered in our plugin. If we take a look at the AST tree:

Everything is wrapped in NewExpression. So unless babel ever decides to change how it parses the tree we shouldn't worry about it.

[tjzel]

I forgor to add () to constructor here, therefore objects with new operator actually have to be handled 👍

[piaskowyk]

I'm just wondering if it is possible to create tests that will check if all names from EntryExitAnimations, LayoutTransitions, BaseAnimationsChainableMethods, and DefaultTransitionChainableMethods are still relevant. I mean, how to detect that someone changes the name of a class/method.

[tjzel]

I've tried to do it but it seems very complicated. TypeScript makes it difficult enough to import (actually require) anything outside plugin's root directory and forces us to use require, therefore we would need to use require on generated lib files 😵