Fix drag event jitter in Component.pointerDragged by using current coordinates

The existing logic in Component.pointerDragged scheduled a callSerially runnable to ensure drag events continue (e.g. for auto-scrolling) even if the pointer is stationary. However, it captured the `x` and `y` arguments from the method call. If multiple drag events occurred rapidly, these scheduled tasks would execute out of order relative to the latest system events, calling pointerDragged with stale coordinates. This caused the drag position to "jump back" to a previous location, resulting in visual jitter and incorrect drag direction detection.

This fix updates the runnable to use `oldx` and `oldy` (instance fields tracking the latest processed drag position) instead of the captured arguments. This ensures that when the delayed task executes, it uses the most up-to-date position, effectively preventing the replay of stale coordinates.

Author: google-labs-jules[bot]

CodenameOne/src/com/codename1/ui/Component.java

@@ -5083,7 +5083,7 @@ private void pointerDragged(final Component lead, final int x, final int y, fina
                 Display.getInstance().callSerially(new Runnable() {
                     public void run() {
                         if (dragActivated) {
-                            lead.pointerDragged(x, y, currentPointerPress);
+                            lead.pointerDragged(oldx, oldy, currentPointerPress);
                         }
                         dragCallbacks--;
                     }