fix(credentials): report an oversized Databricks token success as a 502

An oversized 2xx token reply carried status 200 into provider_unavailable
and its logs. A refusal keeps its own status.

Author: waleedlatif1

apps/sim/lib/credentials/databricks-service-account.server.test.ts

@@ -194,6 +194,7 @@ describe('getting a Databricks token for a run', () => {
 
     await expect(resolveDatabricksCredentialToken('cred-1')).rejects.toMatchObject({
       code: 'provider_unavailable',
+      status: 502,
       logDetail: { reason: 'Databricks token response exceeded the size limit' },
     })
   })

apps/sim/lib/credentials/databricks-service-account.server.ts

@@ -153,9 +153,10 @@ async function requestWorkspaceToken(
     if (error instanceof SyntaxError) return {}
     signal?.throwIfAborted()
     if (isPayloadSizeLimitError(error)) {
+      // A refusal's status still holds; an oversized success is the provider misbehaving.
       throw new DatabricksCredentialError(
         'Databricks token response exceeded the size limit',
-        response.status
+        response.ok ? 502 : response.status
       )
     }
     // An interrupted body says nothing about the credential, whatever the status line was.