fix(wdio-browserstack-service): exclude action from a11y command wrapping (SDK-6265)

[harshit-browserstack]

What

With @wdio/browserstack-service and accessibility: true, WebdriverIO's Actions API breaks at runtime:

• browser.action('pointer').move(...) → TypeError: browser.action(...).move is not a function
• browser.keys(Key.Tab) → TypeError: keyAction.down is not a function
• browser.moveTo() fails the same way.

The identical code works with accessibility: false. Reported by RS Components (SDK-6265 / A11Y-11325).

Root cause

The accessibility command wrapper (commandWrapper) is declared async, so it always returns a Promise. It is installed over every command in the server-supplied commandsToWrap list — which includes action. But WebdriverIO's browser.action() is synchronous: it returns a chainable PointerAction/KeyAction builder. Wrapping it in an async function makes browser.action('pointer') resolve to Promise<PointerAction>, so .move()/.down() are undefined. browser.moveTo() and browser.keys() are implemented on top of action(), so both break too. Already-async commands (keys, actions, moveTo) are unaffected.

Fix

Exclude action — the only synchronous chainable command — from a11y wrapping, in both install sites (direct flow accessibility-handler.ts and CLI/gRPC flow accessibilityModule.ts). Accessibility scan coverage is unchanged (already-async commands stay wrapped).

Verification

• Reproduced the break on WDIO 9 + @wdio/browserstack-service with accessibility: true; control (accessibility: false) passes.
• Built this exact change from source and ran it on a real BrowserStack accessibility session: the Actions API commands now succeed, the test passes, and the a11y report still generates (far-side session userStatus: passed).

🤖 Generated with Claude Code

[harshit-browserstack]

Closing in favour of a backend-side fix: the A11y backend will drop the action entry from the WebdriverIO commandsToWrap list (SDK-6265 / A11Y-11325). That resolves all existing WebdriverIO customers immediately with no SDK upgrade. Keeping the branch (fix/sdk-6265-a11y-action-command-wrapping) around in case we later want the SDK-side guard (refuse to async-wrap synchronous commands) as defense-in-depth.