fix(appium): silence "Method is not implemented" log spam from isDisplayed

webdriverio v9 implements element.isDisplayed() by injecting a JS
visibility check via POST /execute/sync. Appium's native context has no
JS engine, so every call lands a "Method is not implemented" error in
the wdio logger before the existing _isDisplayedSafe catch swallows it.

Tests pass but logs are noisy with these false-positive errors during
seeElement, click, grabTextFrom, grabAttributeFrom, etc.

Override isDisplayed at the element level: short-circuit to true while
in native context so the failing request is never issued. Matches the
semantics _isDisplayedSafe already applies (treats "not implemented" as
displayed since we found the element). In web/webview context, defer
to the original implementation.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Author: DavertMik

lib/helper/Appium.js

@@ -334,6 +334,24 @@ class Appium extends Webdriver {
     }
     this.$$ = this.browser.$$.bind(this.browser)
 
+    // wdio v9 implements `element.isDisplayed()` for non-mobile contexts by
+    // injecting a JS visibility check via POST /execute/sync. Appium's native
+    // context cannot execute JS, so each call logs an ugly
+    // "Method is not implemented" ERROR before the existing catch swallows it.
+    // Short-circuit isDisplayed to `true` while in native context so the
+    // request is never issued (matches existing _isDisplayedSafe semantics).
+    const helper = this
+    if (typeof this.browser.overwriteCommand === 'function') {
+      this.browser.overwriteCommand(
+        'isDisplayed',
+        async function (origFn, ...args) {
+          if (helper.isWeb) return origFn.call(this, ...args)
+          return true
+        },
+        true,
+      )
+    }
+
     this.isRunning = true
     if (this.options.timeouts && this.isWeb) {
       await this.defineTimeout(this.options.timeouts)