Fix drag vs align

[zsoltk]

Description

Related to #539

Issue that arose in that PR's context

• boundsInParent() gives an offset relative to 0,0 in parent – this offset is what we use to setup the gesture detection area
• .align(), if present in the elementUiModel modifiers will also affect the gesture detection area's alignment though, and we can't turn it off, because:
• .align() can only be set once in compose (or more precisely, the first one takes priority, any subsequent invocations are ignored), which means we couldn't do the same trick as with offset (+offset, gesture, -offset) to temporarily disable alignment
• but without turning it off temporarily the effect is that boundsInParent() offset is always relative to 0,0 whereas it should be relative to the alignment point, resulting in a wrong target area being calculated

Approach that was implemented instead:

• A Box was extracted from Child to apply the gesture detection on – this way it can remain unaffected by alignment change

The problem with the approach

• If Child has any gesture-related code (e.g. click), pointer input handling can't properly reach the Box by bubbling up, since it's not a parent to Child but a sibling in the hierarchy
• Dragging the AppyxComponent would break in this case and no longer do anything

New solution

• Revert back to using a single composable
• Detecting if PositionInside/PositionOutside MotionProperty are present
• Fetch their the alignment-related offset (relative to 0,0) and account for it in the offset calculation for the gesture

Result

• Click + Drag works properly
• Drag detection area is calculated properly

...

Check list

• I have updated CHANGELOG.md if required.
• I have updated documentation if required.

[manuel-martos]

What about importing PositionInside.Value and PositionOutside.Value using aliases to make this code more orthogonal? Something like this:

import com.bumble.appyx.interactions.core.ui.property.impl.position.PositionInside.Value as PositionInsideValue
import com.bumble.appyx.interactions.core.ui.property.impl.position.PositionOutside.Value as PositionOutsideValue
// ...
val positionInside = motionPropertyRenderValue<PositionInsideValue, PositionInside>()
val positionOutside = motionPropertyRenderValue<PositionOutsideValue, PositionOutside>()

[manuel-martos]

Same could be applied here.

[manuel-martos]

What about moving this elementOffset composable somewhere common but internal?

[zsoltk]

As part of #534 we can keep only one rather than moving out.