fix(test): use zero retries for error handling test

The upload error test was flaky because pRetry now tracks the latest
error (not the first). With retries enabled, nock's single interceptor
gets consumed on the first attempt, causing retry attempts to throw
Nock: No match instead of ResponseError.

Author: jdalton

test/unit/socket-sdk-upload.test.mts

@@ -379,6 +379,11 @@ describe('SocketSdk - Upload Manifest', () => {
       'should handle errors in uploadManifestFiles',
       { retry: 2 },
       async () => {
+        const noRetrySdk = new SocketSdk('test-token', {
+          ...FAST_TEST_CONFIG,
+          retries: 0,
+        })
+
         nock('https://api.socket.dev')
           .post('/v0/orgs/test-org/upload-manifest-files')
           .reply(400, {
@@ -387,7 +392,7 @@ describe('SocketSdk - Upload Manifest', () => {
             },
           })
 
-        const result = await sdk.uploadManifestFiles('test-org', [
+        const result = await noRetrySdk.uploadManifestFiles('test-org', [
           packageJsonPath,
         ])