Problem

The previous clearInput implementation used tripleTap on element coordinates, which failed with dynamic input fields like eBay's search box that shows a new input overlay when clicked.

Root cause: When aiInput was called after the dynamic input appeared:

1. AI located the original search box coordinates (stale)
2. clearInput used tripleTap on those stale coordinates
3. The tap hit the wrong element, breaking focus on the dynamic input field
4. Text input failed

Solution

Replaced the coordinate-based clearing approach with WebDriver's standard Clear API:

// New approach:
1. Get currently focused element using /element/active endpoint
2. Clear it using /element/{id}/clear endpoint

Benefits

✅ Works with dynamic input fields - Uses element references instead of coordinates
✅ No unwanted events - WebDriver's clear is an atomic operation
✅ W3C standard - Uses official WebDriver protocol
✅ Simpler code - Removed tripleTap and backspace fallbacks

Changes

packages/ios/src/ios-webdriver-client.ts

Added three new methods:

• getActiveElement() - Get WebDriver ID of focused element
• clearElement(elementId) - Clear element by ID
• clearActiveElement() - Combined method for easy use

packages/ios/src/device.ts

Simplified clearInput() to use clearActiveElement()

Test files

Updated test files across platforms to use consistent search action descriptions

Testing

Tested with eBay's dynamic search box which previously failed consistently.

Note: This PR cherry-picks the changes from PR #1403 (merged to 1.0 branch) to the main branch.