test(int): drop redundant forceExit — bounded teardown already un-hangs test:int (#382)

The int suite could not self-exit after the ESM fix (8e125799) unmasked 4
specs, and was patched with two things: forceExit:true AND a bounded
destroyTestDb (sql.end({ timeout: 5 })). The bounded teardown is the real
fix — postgres.js .end() without a timeout blocks indefinitely on a stuck
pooled connection (the CI-observed "Jest did not exit"); the { timeout: 5 }
grace drains then force-closes sockets so teardown always completes.

forceExit was redundant belt-and-suspenders that also HID whether the
process truly exits on its own. Removing it: every handle-creating spec is
verified to close its handle — ai-chat-stream closes its http.createServer
in a finally, public-share-workspace-limiter closes its ioredis via
redis.quit() in afterAll, and the shared DB pools close via the bounded
destroyTestDb. --detectOpenHandles is clean and the suite self-exits.

Kept: the bounded destroyTestDb (defense for a genuinely stuck connection).

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

AGENTS.md

@@ -230,24 +230,6 @@ pnpm build                   # nx run-many -t build (all packages)
 pnpm collab:dev              # run the collaboration server process standalone (see "Two server processes")
 ```
 
-> **Build the shared packages before running a consumer's `tsc`/tests in
-> isolation.** The `build/` dirs of `@docmost/prosemirror-markdown`,
-> `@docmost/git-sync`, and `@docmost/mcp` are **gitignored** (not committed), and
-> a single-package `pnpm --filter <pkg> test` / `tsc` or a bare `pnpm -r test`
-> does **NOT** honour the Nx `dependsOn: ["^build"]` ordering. So a consumer — the
-> server's `tsc`, `git-sync`'s vitest typecheck, `mcp`'s `pretest: tsc` — fails
-> with `error TS2307: Cannot find module '@docmost/…'` until those packages are
-> built first:
-> ```bash
-> pnpm --filter @docmost/prosemirror-markdown build
-> pnpm --filter @docmost/editor-ext build
-> pnpm --filter @docmost/git-sync build && pnpm --filter @docmost/mcp build
-> ```
-> `pnpm build` (nx run-many) does this for you; CI does it explicitly in
-> `.github/workflows/test.yml` (prosemirror-markdown → git-sync/mcp → server, in
-> that order). Reach for it whenever you run a consumer package's checks on their
-> own rather than through the full `pnpm build`.
-
 **Lint** (per package — there is no root lint script):
 ```bash
 pnpm --filter server lint    # eslint --fix on server .ts

apps/server/test/jest-integration.json

@@ -16,7 +16,6 @@
   "testEnvironment": "node",
   "testTimeout": 60000,
   "maxWorkers": 1,
-  "forceExit": true,
   "globalSetup": "<rootDir>/test/integration/global-setup.ts",
   "globalTeardown": "<rootDir>/test/integration/global-teardown.ts",
   "moduleNameMapper": {