Increase Bun csvDataLoad timeout from 60s to 120s

On Bun shard 2, the embed-directive test suite tears down its Harper instance
(flushing HNSW index data to disk) concurrently with northwind's csvDataLoad
background job. The CPU-intensive HNSW flush starves the job processor, causing
it to still be IN_PROGRESS at the 60s polling deadline. 120s gives the flush
time to complete before the assertion fires.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: kriszyp

integrationTests/apiTests/northwind.test.mjs

@@ -2160,7 +2160,7 @@ suite('Northwind operations', { skip: skipSuite }, (ctx) => {
 		// Use awaitJob + manual assertions so we can return job.message as a raw
 		// object — awaitJobCompleted would stringify it, breaking callers that
 		// access errorMsg.unauthorized_access / errorMsg.invalid_schema_items.
-		const jobResp = await awaitJob(client, getJobId(r.body), isBunRuntime ? 60 : 30);
+		const jobResp = await awaitJob(client, getJobId(r.body), isBunRuntime ? 120 : 30);
 		const job = jobResp.body[0];
 		assert.ok(job, `No job found in response: ${jobResp.text}`);
 		if (_expectedError) {