Feat/add transition animator

[M-i-k-e-l]

Depends on

#1475

Description

Add TransitionView - a wrapping view that adds enter\exit animation (incubator).

I know there's a few location === 'left' || location === 'right' (or top and bottom), but to move it to a method I'll need to have two versions (worklet and regular), and I'll have to add ! in some places.
I'm unsure if we can use useHiddenLocations elsewhere, and about the naming of HiddenLocation (I've renamed it to TransitionLocation in TransitionView).

A few other things:

1. There's a question (a TODO) about how to handle opacity from the user.
2. We can allow the user to add his\her own animation. Edit: I probably need to select a different animation (time probably) for this, I don't want to block this PR with this though, it'll be easier to test with future PRs (Dialog?).
3. The usage of TransitionLocation in the screen is a bit clunky, not sure if I did something wrong or if using a union is less usable than an enum, WDYT?

Changelog

Add TransitionView - a wrapping view that adds enter\exit animation (incubator).

[ethanshar]

See my comments.
I mostly focused on readability and code structure.

I'm curious if this API will fit to our use cases.
(I mean the imperative API over the declarative one)

[M-i-k-e-l]

I've renamed and refactored a few things, let me know if anything else comes to mind.

[ethanshar]

The arguments order here feels a little weird.
You have to the end callback and then the direction..
Don't you think it's more appropriate to have (to, direction, endCallback) ?

[M-i-k-e-l]

Yes, but the direction can be undefined and A required parameter cannot follow an optional parameter.

[ethanshar]

Why is direction argument undefined?
In animate implementation, the method does nothing if direction was not passed...
Also, in all usages, you always pass the direction.

[M-i-k-e-l]

I guess you're right, fixed.