Override layoutcomponent x/y using layoutX/Y

Duo called out a bug where a translation constraint applied to a layout component behaved differently in editor vs runtime. The issue was due to the constraint using x/y properties, whereas layoutX/Y should be used for layout components. Added an override to fix this.

Checked other usages of x/y() in CPP and currently, the only place they are used that is applicable to layout components is in constraints and ListenerAlignTarget.

Diffs=
e8d6e5db26 Override layoutcomponent x/y using layoutX/Y (#8714)

Co-authored-by: Philip Chung <philterdesign@gmail.com>

.rive_head

@@ -1 +1 @@
-d3f6a49778aa6ce7408aecededeb1afc1bf33e6e
+e8d6e5db26279ca460b46161df84c77f73903a95

include/rive/layout_component.hpp

@@ -191,8 +191,10 @@ class LayoutComponent : public LayoutComponentBase,
                               m_layout.height());
     }
 
-    float layoutX() { return m_layout.left(); }
-    float layoutY() { return m_layout.top(); }
+    float x() const override { return layoutX(); }
+    float y() const override { return layoutY(); }
+    float layoutX() const { return m_layout.left(); }
+    float layoutY() const { return m_layout.top(); }
     float layoutWidth() { return m_layout.width(); }
     float layoutHeight() { return m_layout.height(); }
     float innerWidth()