node:util: cancellation helper parity cut #3427

Summary

Group the Node-compatible node:util cancellation helpers into one medium PR cut. These helpers are small individually, but they share AbortSignal lifecycle behavior and should be implemented together rather than reviewed as unrelated one-off exports.

Child Issues

• node:util: expose transferable AbortSignal helpers #3419 — node:util: expose transferable AbortSignal helpers
• node:util: implement aborted AbortSignal promise helper #3426 — node:util: implement aborted AbortSignal promise helper
• globals: complete AbortSignal static helpers and abort lifecycle #2582 — global AbortController / AbortSignal lifecycle and static helper behavior needed by the util helpers

Intended PR Boundary

Implement the util-facing cancellation helper surface:

• util.transferableAbortController()
• util.transferableAbortSignal(signal)
• util.aborted(signal, resource)
• the minimum AbortSignal lifecycle behavior needed for those helpers to observe abort state, reason, and abort events like Node

The PR should include focused parity tests for the child issue repros and update any manifest/docs/known-failure entries it touches.

Non-goals

• Full worker_threads structured-clone or MessagePort implementation
• Stream pipeline abort semantics outside helper interaction
• Unrelated node:util formatting, dotenv, debug, system-error, or MIME helper work
• Broad AbortSignal rewrites beyond behavior required by the child issues

Acceptance

• child issues node:util: expose transferable AbortSignal helpers #3419 and node:util: implement aborted AbortSignal promise helper #3426 have passing parity/regression coverage
• any AbortSignal behavior taken from globals: complete AbortSignal static helpers and abort lifecycle #2582 is covered at the point used by the util helpers
• node:util manifest/declaration/runtime paths expose the helpers consistently for namespace, named import, and captured-call forms
• implementation matches Node observable behavior for helper return values, abort propagation, and reason/event handling