feat(longPressOn): add configurable duration parameter

[Matheeusb]

Summary

Fixes #3083

The longPressOn command had a hardcoded 3-second duration with no way to configure it. This prevented users from automating workflows that require longer (or shorter) press durations, such as bypassing Human Security challenges that require extended presses.

Changes

New YAML API

Users can now specify a duration field (in milliseconds) on longPressOn:

# Custom duration (8 seconds)
- longPressOn:
    id: "my_button"
    duration: 8000

# Works on text selectors too
- longPressOn:
    text: "Hold to confirm"
    duration: 5000

# Works on screen coordinates
- longPressOn:
    point: "50%,50%"
    duration: 2000

# Backward compatible — omitting duration keeps the existing 3s default
- longPressOn: "Some element"

Modules changed

Module	Change
maestro-orchestra-models	Added duration: Long? to TapOnElementCommand, TapOnPointV2Command, TapOnPointCommand; added DEFAULT_LONG_PRESS_DURATION_MS = 3000L constant
maestro-client	Updated Driver interface: longPress(point, durationMs = 3000L); propagated longPressDurationMs through all tap() overloads and into hierarchyBasedTap/screenshotBasedTap
maestro-client (drivers)	AndroidDriver, IOSDriver, WebDriver, CdpWebDriver — all now use the passed durationMs instead of the hardcoded 3000
maestro-orchestra	YamlElementSelector — new duration field; YamlFluentCommand — extracts and passes duration; Orchestra — passes command.duration to all tap call sites
maestro-test	FakeDriver.Event.LongPress now captures durationMs for test assertions

Tests

• Added 033_longPressOn_withDuration.yaml fixture covering duration on element-by-text, element-by-id, default (null), and screen-point variants
• Added longPressOn with custom duration should parse duration into command test in YamlCommandReaderTest

Backward compatibility

Fully backward compatible. Omitting duration preserves the existing 3000ms default behaviour.