fix(textract): pass through the real upstream status for filePath fetch failures

fetchDocumentBytes hardcoded 400 for any non-OK response from a document
URL, masking transient 5xx failures from the document host as client
errors and blocking tool-execution retries. Use the actual response
status instead.

Author: waleedlatif1

apps/sim/app/api/tools/textract/shared.ts

@@ -102,7 +102,12 @@ async function fetchDocumentBytes(url: string): Promise<{ bytes: Buffer; content
   })
   if (!response.ok) {
     await response.text().catch(() => {})
-    throw new TextractRouteError(`Failed to fetch document: ${response.statusText}`, 400)
+    // Pass through the document host's real status (e.g. a transient 503) instead of a
+    // hardcoded 400, so tool-execution retry logic can still treat 5xx as retryable.
+    throw new TextractRouteError(
+      `Failed to fetch document: ${response.statusText}`,
+      response.status
+    )
   }
 
   const arrayBuffer = await response.arrayBuffer()