fix: resolve TypeScript linting error with proper error type

Replace 'any' type with proper Error type definition including
optional Node.js error properties (code, errno, syscall, path).

This fixes the ESLint @typescript-eslint/no-explicit-any violation
and unblocks CI.

Author: CI Bot

packages/adapter-python/src/utils/python-utils.ts

@@ -86,7 +86,12 @@ class WhichCommandFinder implements CommandFinder {
       return resolved;
     } catch (error) {
       if (process.env.CI === 'true' || process.env.DEBUG_PYTHON_DISCOVERY) {
-        const err = error as any;
+        const err = error as Error & {
+          code?: string;
+          errno?: number;
+          syscall?: string;
+          path?: string;
+        };
         console.error(`[Python Discovery] which failed for ${cmd}:`, {
           message: err.message,
           code: err.code,