Class DelayedPushChannelTransfer<T>

Reactive channel with delayed emission to subscribers on push().

Capabilities: isInput, isOutput, isPushable, isSubscribable

Mechanics:

1. push(data) — schedules a timer for delay ms; on expiry, writes the value to _state, notifies subscribers, clears _state
2. subscribe(handler) — subscribes to notifications
3. destroy() — clears all pending timers, unsubscribes subscribers, clears state

Each push() gets its own timer — multiple push() calls result in multiple delayed notifications.

Configuration (DelayedPushChannelTransferConfig):

• delay: number — delay before emitting data to subscribers (ms)

Difference from PushChannelTransfer:

• push() does NOT notify subscribers immediately — only after delay ms
• The value is captured in the timer closure, so multiple push() calls do not overwrite each other's data

Use cases:

• Delayed events (e.g., debounce-like delay without suppression)
• Asynchronous emission with a guaranteed delay
• Testing reactive chains with a time shift