Pubsub UND_ERR_BODY_TIMEOUT in Docker: undici 7→8 global-dispatcher symbol split

[Rinse12]

Summary

The daemon (Docker / this branch) logs recurring pubsub errors:

pkc-js:...:pubsubSubscribeOnProvider:error pubsub callback error ... TypeError: terminated
[cause]: BodyTimeoutError: Body Timeout Error (UND_ERR_BODY_TIMEOUT)
  at .../@libp2p/http/node_modules/undici/lib/dispatcher/client-h1.js

It does not reproduce when running the published CLI via a host npm install.

Root cause (verified empirically)

An idle long-poll HTTP stream is aborted by undici's default 5-minute bodyTimeout. pkc-js
ships a polyfill that disables this:

// pkc-js/dist/node/runtime/node/polyfill.js
setGlobalDispatcher(new Agent({ bodyTimeout: Number.MAX_SAFE_INTEGER }))

But undici changed its global-dispatcher symbol between v7 and v8:

undici	get/setGlobalDispatcher slot
7.x	Symbol.for('undici.globalDispatcher.1')
8.x	Symbol.for('undici.globalDispatcher.2') (.1 legacy only)

setGlobalDispatcher writes the slot of whichever undici is hoisted to top-level:

• This branch / Docker: top-level undici is 7.25.0 (hoisted for open-graph-scraper@^7
  • cheerio@^7); @libp2p/http@^8.0.3 is nested on its own undici 8.x. pkc writes .1;
    the helia / @libp2p/http request reads .2 (never set) → default 300s → timeout.
• Host install: top-level undici is 8.x; pkc writes .2; the @libp2p/http request
  reads .2 = pkc's MAX-bodyTimeout agent → no timeout.

The kubo-rpc-client pubsub long-poll itself uses native global fetch (reads .1) and is
covered by the polyfill; the timing-out request is the undici-8.x / @libp2p/http (helia) path.

Fix

Hoist undici 8.x to top-level (mirroring the working host layout) so pkc's polyfill writes the
.2 slot that the @libp2p/http path reads — add a direct undici@^8 dependency; ^7
consumers (cheerio, open-graph-scraper) keep their own nested 7.x copies.

Likely surfaced by the kubo 0.41→0.42 dependency bump on this branch re-hoisting undici to 7.x.

[Rinse12]

Fix applied (pending review)

Added a direct undici dependency pinned to 8.4.1 (exact) so undici 8.x wins the
top-level hoist. Resulting layout now mirrors the working host install:

• top-level undici → 8.4.1
• @libp2p/http → deduped to top-level 8.4.1 (no nested copy)
• cheerio / open-graph-scraper (undici@^7) → keep their own nested 7.27.2

pkc-js's polyfill now imports top-level undici 8.x → writes the .2 global-dispatcher slot
that the @libp2p/http path reads → idle pubsub streams inherit bodyTimeout: MAX.

Verified in a node:22-slim container against the updated tree: setting the global
dispatcher via the top-level 8.x copy now governs an @libp2p/http-style undici request
(pre-fix it did not).

Regression test: test/cli/undici-dispatcher-hoisting.test.ts asserts top-level undici is
major ≥ 8 and that @libp2p/http resolves to the same major (same dispatcher symbol). Fails
on the pre-fix 7.25.0 / 8.2.0 split, passes now. npm run build + build:test pass.

Note: npm install also reconciled a pre-existing lockfile drift (a missing @types/react
entry that was breaking npm ci).

[Rinse12]

Fix submitted as PR #85 (branched off master): pins a direct undici@8.4.1 so 8.x wins the top-level hoist and pkc-js's polyfill writes the .2 slot the @libp2p/http path reads. Full npm run test:cli passes (29 files, 211 passed, 1 skipped).