Extend the set of layout animation mocks

[jalooc]

Summary

This PR extends #3801 by introducing layout animation types and modifiers that those animation types require to be fully functional.

Currently, the tests fail with something like:

TypeError: Cannot read properties of undefined (reading 'delay')

 > 107 |   const transition = CurvedTransition.delay(10).duration(10),
       |                                       ^

Test plan

Creating a test (e.g. using React Native Testing Library) of a component containing any of the freshly added layout animation types and / or chained modifiers they support. E.g.:

const MyComponent = () => (
  <Animated.View layout={CurvedTransition.delay(10).duration(10)} />
)

test('test the test', () => {
  const screen = render(<MyComponent />)
})

The above example fails before the patch from this PR is introduced and succeeds afterward.

Question

One question to resolve is how closely the mocks should match the real api in the context of which modifiers apply to which animation types (e.g. not all animation types support .stiffness()). Doing so would require more complex mocks that are also harder to maintain for the need to keeping them in sync. An alternative, simpler approach is to add all the modifiers to all the animations - I figure it's okay since these kinds of mocks are not directly consumed in the tests - they just serve enabling test-rendering components utilising layout animations without errors. The latter is the approach I went with, but lmk if you think the other one is a better fit.

[piaskowyk]

@jalooc thanks for your PR! 🙌 When it comes to mocks, I think that they should be as simple as possible because mocks don't contain any logic. So adding modifiers to all the animations is fine for me.