fix: narrow NotFound handling to exclude missing cwd in AzureDevOpsCli

VcsProcessSpawnError with a NotFound platform cause can be triggered by
either a missing executable or a non-existent working directory. The
previous check only tested reason._tag === 'NotFound', which
incorrectly diagnosed bad cwd paths as 'az CLI not available'.

Add two additional guards mirroring the pattern in GitVcsDriverCore:
- pathOrDescriptor !== context.cwd excludes fs.access cwd validation
- syscall !== 'chdir' excludes the rare spawn-level cwd failure

Author: cursoragent

apps/server/src/sourceControl/AzureDevOpsCli.ts

@@ -94,7 +94,9 @@ export class AzureDevOpsCommandFailedError extends Schema.TaggedErrorClass<Azure
     if (
       cause._tag === "VcsProcessSpawnError" &&
       cause.cause instanceof PlatformError.PlatformError &&
-      cause.cause.reason._tag === "NotFound"
+      cause.cause.reason._tag === "NotFound" &&
+      cause.cause.reason.pathOrDescriptor !== context.cwd &&
+      cause.cause.reason.syscall !== "chdir"
     ) {
       return new AzureDevOpsCliUnavailableError(fields);
     }