fix(parser): Ensure sequential command extraction order

Refactored CommandParser.kt to correctly parse commands based on their order of appearance in the input text.

Previously, commands were searched by type in a fixed sequence, which could lead to commands being extracted in a different order than they were written if multiple command types were present in a single message.

The new implementation:
- Consolidates all regex patterns with associated command builders.
- Finds all potential matches for all patterns in the input text.
- Sorts these matches by their start index.
- Iterates through the sorted matches, selecting the first valid, non-overlapping command, thus preserving the original sequence.
- Retains logic for ensuring certain parameterless commands (e.g., TakeScreenshot) are only added once per parsing operation.

This change is crucial for ensuring that the command execution queue receives commands in the intended sequence.

Author: google-labs-jules[bot]

app/src/main/kotlin/com/google/ai/sample/ScreenOperatorAccessibilityService.kt

@@ -115,8 +115,9 @@ class ScreenOperatorAccessibilityService : AccessibilityService() {
             serviceInstance!!.commandQueue.add(command)
             Log.d(TAG, "Command $command added to queue. Queue size: ${serviceInstance!!.commandQueue.size}")
 
-            if (!serviceInstance!!.isProcessingQueue.get()) {
-                 serviceInstance!!.processCommandQueue() // Call the instance method
+            // Ensure processCommandQueue is called on the service's handler thread
+            serviceInstance!!.handler.post {
+                serviceInstance!!.processCommandQueue()
             }
         }