test(terminology): force serial execution to fix Bun concurrency flake

Bun's node:test implementation can run tests within a suite concurrently.
csv_data_load jobs stall on Bun (known issue), blocking the Harper instance
while concurrent drop_table tests fire against the same server — causing 500
failures and cascading suite timeouts.

Setting concurrency: false on the suite guarantees sequential execution,
matching the assumed serial ordering of the tests.

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

Author: kriszyp

integrationTests/apiTests/terminology.test.mjs

@@ -20,7 +20,7 @@ import { awaitJobCompleted } from './utils/operations.mjs';
 // Resolve the CSV fixture path relative to this file so Harper can read it.
 const SUPPLIERS_CSV = path.join(path.dirname(fileURLToPath(import.meta.url)), 'data/Suppliers.csv');
 
-suite('Terminology aliases (database / primary_key)', (ctx) => {
+suite('Terminology aliases (database / primary_key)', { concurrency: false }, (ctx) => {
 	let client;
 
 	before(async () => {