chore: pin test deps to yarn-locked versions

ts-jest, jest, jest-environment-node-single-context, @types/jest, and
lodash drifted upward when Bun resolved fresh against the ^x.y.z
ranges. ts-jest 29.4 in particular was 35x slower at compiling the
test suite (~1s under 29.1.1, >30s under 29.4.9), which pushed the CI
test step past the 2-minute timeout.

Pins them to the exact versions yarn.lock had to keep test behavior
unchanged across the package-manager swap.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: bonustrack

bun.lock

@@ -39,7 +39,7 @@
     "dotenv": "^16.0.2",
     "express": "^4.18.1",
     "express-rate-limit": "^6.9.0",
-    "lodash": "^4.17.21",
+    "lodash": "4.17.21",
     "mysql": "^2.18.1",
     "node-fetch": "^2.7.0",
     "rate-limit-redis": "^3.1.0",
@@ -56,16 +56,16 @@
   "devDependencies": {
     "@snapshot-labs/eslint-config": "0.1.0-beta.18",
     "@snapshot-labs/prettier-config": "0.1.0-beta.7",
-    "@types/jest": "^29.5.2",
+    "@types/jest": "29.5.2",
     "@types/node": "^16.0.0",
     "dotenv-cli": "^7.2.1",
     "eslint": "^8.28.0",
-    "jest": "^29.6.1",
-    "jest-environment-node-single-context": "^29.1.0",
+    "jest": "29.6.1",
+    "jest-environment-node-single-context": "29.1.0",
     "nodemon": "^2.0.19",
     "prettier": "3.0.3",
     "start-server-and-test": "^2.0.0",
     "supertest": "^6.3.4",
-    "ts-jest": "^29.1.1"
+    "ts-jest": "29.1.1"
   }
 }