chore: upgrade kubo 0.41.0 → 0.42.0

[Rinse12]

Goal

Upgrade the bundled kubo dependency from 0.41.0 to 0.42.0 (latest official release, published by the ipfs/npm-kubo GitHub Actions pipeline; maps to kubo binary v0.42.0).

Changelog review vs. our usage

Reviewed the v0.42.0 release notes against how bitsocial-cli uses kubo (src/ipfs/startIpfs.ts): ipfs init, ipfs config profile apply server, ipfs repo migrate, ipfs daemon --enable-namesys-pubsub --migrate, plus config edits to Addresses, AutoTLS.Enabled, and Gateway.PublicGateways.

Findings — no breaking changes affect us:

• Provide.DHT.Interval=0 semantics change (the only breaking change): daemon now refuses startup if Provide.DHT.Interval=0 is set without explicit Provide.Enabled. We never set Provide.* in our config merge and don't rely on the server profile touching it. Not applicable.
• --enable-namesys-pubsub / --migrate: still valid in 0.42.0, not deprecated/removed.
• ipfs repo migrate: still works; now more resilient (retry across gateways, HTTP timeouts).
• ipfs routing provide deprecated: we don't use it.
• New optional settings (Internal.ShutdownTimeout default 12h, Migration.DownloadSources, Provide.DHT.SendProviderRecordTimeout) and new RPC subcommands (provide once, diag healthy, dag export/import --local-only) don't affect existing usage.

Notes

• Avoided npm kubo@1.0.1 — hand-published by an individual rather than the official GitHub Actions pipeline; kubo binary releases follow 0.x.0.

Verification

• npm run build && npm run build:test ✅
• npm run test:cli ✅ (259 passed, 1 skipped; includes daemon/kubo restart-race suites that drive the real kubo binary, confirmed running ipfs version 0.42.0)

[Rinse12]

Implemented in #81 — upgraded kubo 0.41.0 → 0.42.0, changelog reviewed (no breaking changes affect our usage), build + full test:cli pass driving the real 0.42.0 binary.