feat(runner): tap, swipe and fill in runner actions sequences (AGE-5427)

[Erzhan Torokulov (erzhtor)]

Relates to AGE-5427. Platform side: qawolf/platform#34509 (not merged yet; publishes @qawolf/api-contracts 0.78.0). Follows #1638.

Overview of Changes

After #1638, runner actions said it takes "the same actions runner act takes", but it checked each step against the browser-only schema. That meant tap, swipe and fill were refused locally before any request went out. Contracts 0.78.0 widens the sequence contract to every runner action, so this PR:

• validates each step with parseRunnerAction, the same check runner act uses (and drops the now-unused parseBrowserAction)
• reports the new action-not-supported-on-browser step reason (exit code 2), for when a browser runner refuses a mobile step; with --continue-on-failure the rest still runs
• adds mobile examples to runner actions --help

The description is unchanged, because it is now accurate.

Testing

Ran against a local pack of 0.78.0 built from qawolf/platform#34509: typecheck, lint, format:check, knip and test pass, except 3 keychain tests that also fail on main on this machine. New tests are in performActions.touchscreen.test.ts.

To Do

• Wait for qawolf/platform#34509 to merge and @qawolf/api-contracts 0.78.0 to publish
• Check 0.78.0 still has run acceptScreenshotBaseline, listScreenshotComparisons and restoreScreenshotBaseline. main pins 0.77.0, which was published from the unmerged screenshot stack (qawolf/platform#34307); a 0.78.0 built from platform main without it would drop those commands
• Run bun install to update bun.lock, then bun run generate and commit any SKILL.md drift

Checklist

• Changes follow the code style of this project
• Self-review completed
• Tests added/updated (or not applicable)
• No breaking changes (or described below)