fix(supabase): check response.ok before parsing storage_create_signed_url

Matches the pattern already applied to the new signed-upload-url tool
this session — a non-2xx response now surfaces Supabase's actual error
message instead of the generic "did not return a signed URL path" one.

(cherry picked from commit 9f40427)

Author: waleedlatif1

apps/sim/tools/supabase/storage_create_signed_url.ts

@@ -86,6 +86,12 @@ export const storageCreateSignedUrlTool: ToolConfig<
       throw new Error(`Failed to parse Supabase storage create signed URL response: ${parseError}`)
     }
 
+    if (!response.ok) {
+      throw new Error(
+        `Failed to create signed URL: ${data.message || data.error || response.statusText}`
+      )
+    }
+
     const relativePath = data.signedURL || data.signedUrl
     if (!relativePath) {
       throw new Error('Supabase did not return a signed URL path in its response')