fix(server): use prebuilt node-pty binaries - #6350

💭 I'm reviewing the TypeScript files that are in scope for this change: the desktop backend configuration, WSL environment setup, Node PTY adapter, and pinned runtime handling. The scripts directory is excluded since it's outside the apps, packages, and infra directories.… I'm checking how the code changes align with existing conventions in DesktopWslEnvironment.ts. The main shift is that the exitCode check has moved after the version check, which changes the logic flow — previously the version check only ran when exitCode was 0, but now it runs regardless. It's a behavioral change but doesn't violate any established patterns. For NodePtyAdapter.ts, the createRequire factory parameter is being injected as a test seam rather than a service, which fits the convention… I'm noticing a potential issue where error handling is being too permissive—using Effect.try with a catch handler that returns null, combined with orElseSucceed, effectively swallows real failures without proper typed error definitions, which goes against the convention of explicitly defining failure cases.… I'm noticing that AuthConnectorManager.ts has a lingering import of "node-pty" even though the dependency was removed from the package.json, which is technically a bug. However, this file wasn't modified in the pull request itself, so the question becomes whether this counts as a violation within the scope of what I'm checking for—which is specifically Effect service conventions. Since the file pattern matches but the actual violation isn't convention-related, I need to determine if this falls under "concrete violations introduced or retained in the pull request's changed scope."…