fix(app-management): resolve app names against rehydrated sessions

[Mochxd]

Problem

getInstalledApps looks the driver up with the raw store getter:

const driver = getDriver(sessionId);
if (!driver) {
  throw new Error(noActiveDriverSessionMessage(sessionId));
}

That skips resolveDriver, so it never re-attaches a persisted remote session. After an MCP process recycle, appium_app_lifecycle resolved by name fails with "No active driver session" while the same action by id succeeds on the same session, because the lifecycle handlers (activate, terminate, uninstall, …) call resolveDriver themselves but only after resolveId has already run.

permissions.ts does not hit this, since it calls resolveDriver before resolveAppId.

Fix

Resolve the driver through resolveDriver so name lookups rehydrate the session like every other tool. The thrown message is unchanged when the session genuinely cannot be resolved.

Test

Added src/tests/tools/app-management/resolve-app-id.test.ts:

• with an empty in-memory driver cache, the name is resolved against the rehydrated driver
• an unresolvable session still reports "No active driver session" and never queries the device

[github-actions]

🎉 This PR is included in version 1.92.3 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀