fix(accessibility): patch prototype command for class-based Nightwatch commands

[kamal-kaur04]

Description

performScan never fired on browser.execute('mobile:scroll', ...) — and on every other class-based command listed in commands.json — during App Accessibility sessions. No accessibility scan was captured for those interactions.

Root cause

commandWrapper() patched originalCommand.command directly. That only works for web-element commands, which export a plain object (module.exports.command = fn). But executeScript/executeAsyncScript (and the api/protocol, api/client-commands, and appium commands) export a class with command on the prototype:

class ExecuteScript extends ClientCommand { command(script, args, cb) { ... } }
module.exports = ExecuteScript;

So originalCommand.command read a non-existent static method (originalCommandFn was undefined) and the wrapper assigned a new static method that Nightwatch never calls — it invokes the prototype command. The patch silently no-op'd, no error thrown.

Fix

Detect whether command lives as an own property (object export) or on the prototype (class export) and patch the correct target — mirroring how the protocolAction branch already handles class-based commands.

const commandTarget = typeof originalCommand.command === 'function'
  ? originalCommand
  : (originalCommand.prototype && typeof originalCommand.prototype.command === 'function'
    ? originalCommand.prototype
    : null);

The pre-existing shouldPatchExecuteScript recursion guard (dead code until now, since the patch never attached) becomes effective and prevents the plugin's own browserstack_executor scan scripts from re-triggering a scan.

How tested

• Real-device Android App Accessibility session (@nightwatch/browserstack + appium).
• app.execute('mobile:scroll', ...) now triggers exactly one performScan; instrumented trace confirms PATCH cmd=executeScript target=prototype and FIRE wrapped cmd=executeScript arg0=mobile:scroll.
• No recursion — the 11 internal browserstack_executor: {...appAllyScan...} re-entries all hit the guard and skipped re-scanning.
• Test passes; eslint clean.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature
• Breaking change

[kamal-kaur04]

Merged in #58