Fix(gestures): Handle pointer events inside awaitPointerEventScope

The lint tool reported a "ReturnFromAwaitPointerEventScope" warning
in KotlinSnippets.kt.
Returning a value from this scope can lead to dropped input events
due to the way pointer event queues are handled.

This commit resolves the warning by moving the animation logic,
which depends on the tap position, directly inside the
awaitPointerEventScope block.
This ensures that the event data is processed immediately
within the correct context, preventing potential event loss.

Author: cartland

compose/snippets/src/main/java/com/example/compose/snippets/kotlin/KotlinSnippets.kt

@@ -340,15 +340,17 @@ fun MoveBoxWhereTapped() {
                 // coroutines inside a suspend function
                 coroutineScope {
                     while (true) {
-                        // Wait for the user to tap on the screen
-                        val offset = awaitPointerEventScope {
-                            awaitFirstDown().position
-                        }
-                        // Launch a new coroutine to asynchronously animate to
-                        // where the user tapped on the screen
-                        launch {
-                            // Animate to the pressed position
-                            animatedOffset.animateTo(offset)
+                        // Wait for the user to tap on the screen and animate
+                        // in the same block
+                        awaitPointerEventScope {
+                            val offset = awaitFirstDown().position
+
+                            // Launch a new coroutine to asynchronously animate to
+                            // where the user tapped on the screen
+                            launch {
+                                // Animate to the pressed position
+                                animatedOffset.animateTo(offset)
+                            }
                         }
                     }
                 }