chore: update sporadically failing tests, upgrade tigerbeetle

[mkurapov]

Changes proposed in this pull request

• Update grant pagination tests
• (hopefully) fix BigInt serialization issue during test running
• upgrade tigerbeetle to 0.13.38

Context

Sometimes, we would see this test failure in the CI step, example:

FAIL auth src/grant/service.test.ts
  ● Grant Service › getGrantsPage › Can paginate and filter

    TypeError: Cannot read properties of undefined (reading 'id')

      324 |       )
      325 |
    > 326 |       expect(page[0].id).toBe(grants?.[1].id)
          |                      ^
      327 |       expect(page.length).toBe(1)
      328 |     })
      329 |   })

      at Object.id (packages/auth/src/grant/service.test.ts:326:[22](https://github.com/interledger/rafiki/actions/runs/5455836801/jobs/9927874921#step:5:23))

This is because of the Promise.all: the order for the in-memory grants array was different than what was created in the database.

This also adds a workerThreads: true option to the base jest config, to hopefully resolve the sporadic BigInt serialisation issue:

• (fixes jest expect failure error with BigInt #138)

Checklist

• Related issues linked using fixes #number
• Tests added/updated
• Documentation added
• Make sure that all checks pass

[netlify]

✅ Deploy Preview for brilliant-pasca-3e80ec canceled.

Name	Link
🔨 Latest commit	1e5fb05
🔍 Latest deploy log	https://app.netlify.com/sites/brilliant-pasca-3e80ec/deploys/64a46939a41c3200083f0ae2

[mkurapov]

In order to fix

• jest expect failure error with BigInt #138

• jest-worker fails with "Do not know how to serialize a BigInt" in messageParent.ts instead of showing the actual assertion error message when there are 2 or more test suite files executing in parallel jestjs/jest#11617 (comment) was suggested as a solution

[wilsonianb]

The upstream issue was finally closed

• jest-worker fails with "Do not know how to serialize a BigInt" in messageParent.ts instead of showing the actual assertion error message when there are 2 or more test suite files executing in parallel jestjs/jest#11617

so you might be able to remove workerThreads once the fix is published

[mkurapov]

Tigerbeetle tests are failing now, trying to fix... ✅