Node: report progress and logs from an attached executor

[stromanni]

Wire the Node executor's degraded operations to the side-channel from the core issue.

src/detached.ts currently drops updateProgress and writeTaskLog with a one-time warning. Both should reach the executor handle instead — the same shape isCancelRequested already uses to expose frame-delivered cancels to a running handler, so the seam exists.

getSetting keeps answering null: createTaskCallback's middlewareFor should take its disable list from the job frame rather than from MiddlewareDisableStore, which has no storage to read on an executor.

Durations and numeric fields stay in the Node conventions already used by ExecutorRunOptions.

Done when

test/worker/executorAttach.test.ts asserts, against the hermetic scheduler: currentJob().setProgress() produces a progress frame; currentJob().publish() produces a task_log at level result; and a middleware named in the job frame's disable list does not run. The gated executorAttachServer.test.ts confirms progress reaching storage through the real binary.

Parent issue carries the rationale.

[pratyush618]

Done in #604 (5134fcf). detached.ts installs an executor sink on attach and clears it on teardown, so the queue-level shim reaches the scheduler instead of warning and dropping. The task-callback overrides stay: deps.queue is only the detached stand-in under taskito executor, and an executor started from a process that does have storage would otherwise write progress into its own database. Also adds currentJob().log(message, level?, extra?) — publish was the only route to a task log.