fix(lambdatest): fix session listing and attach-to-session for LambdaTest (TE-13124)

[SahilSawLT]

Summary

Fixes Appium Inspector web browser version support for LambdaTest mobile sessions.

JIRA: TE-13124

Changes

1. Session listing via LTMA API

When the server type is TESTMUAI, fetch running sessions directly from the LambdaTest Test Management API instead of /wd/hub/sessions. This is needed because /wd/hub/sessions only returns App sessions (RD App, VD App) — web sessions (RD Web, VD Web) are not included. The LTMA endpoint returns all 4 mobile surfaces.

The LTMA host is derived from the configured hub host:

• mobile-hub.lambdatest.com → api.lambdatest.com
• hub-{cluster}.lambdatestinternal.com → api-{cluster}.lambdatestinternal.com
• mobile-hub-{cluster}.lambdatestinternal.com → api-{cluster}.lambdatestinternal.com

2. Capabilities unwrapping for manual session ID entry

When the user manually types a session ID (cache-miss path), MHPS returns nested capabilities:

{"value": {"capabilities": {"desired": {"platformName": "Android"}}, "sessionId": "abc"}}

Unwrap after res.value — matching the existing // adjust for TestMu AI-specific format pattern already present in the cached sessions path.

3. appMode fix for web sessions

After attaching to a session, appMode (NATIVE vs WEB) was always NATIVE because sessionCaps.browserName is empty when the user only provided a session ID. Fixed by using driver.capabilities.browserName for attached sessions, which is populated from the actual running session after a successful attach.

Test plan

• RD App session appears in "Attach to Session" list and attaches correctly
• RD Web session appears and attaches with correct appMode (WEB not NATIVE)
• VD App session appears and attaches correctly
• VD Web session appears and attaches with correct appMode
• Desktop Electron app unaffected (no CORS restriction, no code change to Electron path)
• Non-LambdaTest server types unaffected

🤖 Generated with Claude Code