style: prettier --write on review-fixup files

Auto-formatting after the previous review fixups commit. CONTRIBUTING.md
list-item indentation, ArrowResultConverter.test.ts multi-line throw
collapsed to one line, thrift-field-id-validation.test.ts same.

Co-authored-by: Isaac
Signed-off-by: Vikrant Puppala <vikrant.puppala@databricks.com>

Author: vikrantpuppala

CONTRIBUTING.md

@@ -112,6 +112,7 @@ npm run type-check
 A few entries in `package.json` are pinned more tightly than usual. Don't relax these without understanding why.
 
 - **`typescript: "5.5.4"`** (exact, no caret). This pin has both a floor and a ceiling:
+
   - Floor (TS >= 5.0) is required because `uuid@11`'s shipped `.d.ts` uses `export type * from './types.js'`, a TS 5.0+ feature.
   - Ceiling (TS < 5.6) is required because TS 5.6 changed how `@types/node`'s generic `Buffer<TArrayBuffer extends ArrayBufferLike>` declarations get emitted into our published `dist/*.d.ts`. Allowing TS 5.6+ would leak `Buffer<ArrayBufferLike>` into the published types, which fails to compile for consumers on stale `@types/node`.
   - If you bump TS, run `npm run build` and `git diff dist/` and verify no `Buffer<...>` generics appear in any `.d.ts`. If they do, you need to either roll back or also bump `@types/node` consumer expectations (a customer-facing change).

tests/unit/result/ArrowResultConverter.test.ts

@@ -61,9 +61,7 @@ const sampleArrowBatch = [
 // import time, so a wrong CWD must fail clearly rather than producing
 // an opaque ENOENT.
 if (!fs.existsSync('package.json')) {
-  throw new Error(
-    `Expected mocha to be invoked from repo root; CWD=${process.cwd()} has no package.json`,
-  );
+  throw new Error(`Expected mocha to be invoked from repo root; CWD=${process.cwd()} has no package.json`);
 }
 const ARROW_STUBS_DIR = path.resolve('tests/unit/result/.stubs');
 const arrowBatchAllNulls = [

tests/unit/thrift-field-id-validation.test.ts

@@ -20,9 +20,7 @@ describe('Thrift Field ID Validation', () => {
     // file is executed from a non-repo-root CWD (e.g. running a single
     // spec from a subdirectory) instead of producing an opaque ENOENT.
     if (!fs.existsSync('package.json')) {
-      throw new Error(
-        `Expected mocha to be invoked from repo root; CWD=${process.cwd()} has no package.json`,
-      );
+      throw new Error(`Expected mocha to be invoked from repo root; CWD=${process.cwd()} has no package.json`);
     }
   });