Fix move-absolute failing with Element not found on Windows PTZ Pro 2

[jochenwezel]

Observed during manual Windows testing with PTZControlConsole v2.4.2.4:

• move-absolute --x 10 --camera "PTZ Pro 2"
• move-relative --x 10 --camera "PTZ Pro 2" also failed in the original test run before later XU fixes
• Error: Element nicht gefunden. (0x80070490)

Expected result:

• move-absolute should either move the camera or fail with a specific explanation of the missing driver/control capability.

Related commits:

• 0819532 Add camera device info command
• 2551bc1 Add explicit value modes for CLI moves
• 1e63686 Fix Windows Logitech XU commands
• d74dc4b Improve camera info and selection syntax

Needs retest against current main because move-relative was changed after the reported test.

[jochenwezel]

Additional finding from local testing on 2026-06-07:\n\nThe same PTZControlConsole.exe cam-device-info -s 2 command behaved differently depending on how it was launched. From the Codex/agent sandbox process it reported IAMCameraControl (UVC) wird nicht unterstützt. for Zoom/Pan/Tilt. Running the exact same executable and arguments outside the sandbox returned valid raw ranges and current values for a Logitech HD Webcam C525:\n\n- Zoom raw: 1..5, current 5\n- Move X raw: -10..10, current 0\n- Move Y raw: -10..10, current 0\n\nConclusion: DirectShow/IAMCameraControl capability checks may be process/session/sandbox sensitive. For this issue, sandbox results should not be treated as authoritative. The next on-site PTZ Pro 2 test should use the release asset or an unsandboxed interactive shell and include cam-device-info before and after relative movement.\n\nThis also supports testing the new experimental move-seek approach: if cam-device-info can read raw current pan/tilt values on the PTZ Pro 2, move-seek can attempt absolute positioning by issuing relative Logitech movement steps and re-reading current values after each correction.